Force DNS on WAN interface

tda2806 · 2018-06-11T21:04:25.746Z

H/W ar300m
F/W LEDE Reboot 17.01.4 r3560-79f57e422d / LuCI lede-17.01 branch (git-17.290.79498-d3f0685)

Configuration: The router is connected to a wifi open network as a WISP repeater. The router is successfully configured to force clients to use the google DNSs 8.8.8.8 and 8.8.8.4.

Problem: I want to configure the router to use a public DNS over it’s WAN interface as it currently uses the ISP’s DNS which does not resolve some of the openvpn servers.

glitch · 2018-06-12T07:35:13.800Z

tda2806:

I want to configure the router to use a public DNS over it’s WAN interface as it currently uses the ISP’s DNS which does not resolve some of the openvpn servers.

If you have “force DNS” in the AR300M, then as far as I know your ISP router’s DNS are ignored.
Anyhow, the answer is to login to your ISP router and change the DNS setting there (from auto > manual).
I do not recommend using Google DNS - they are very untrustworthy - try this instead:

The Cloudflare Blog – 1 Apr 18

Introducing DNS Resolver, 1.1.1.1 (not a joke)

Get the latest news on how products at Cloudflare are built, technologies used, and join the teams helping to build a better Internet.

Glitch

tda2806 · 2018-06-12T08:13:33.424Z

Thanks for the reply,

as stated, the clients connected via the ar300m use the DNSs as configured on the unit
to clarify, the ar300m is connected to a public, open, un-encrypted wifi network and I have no access to the ISPs local or remote equipment. As a consequence of this I am also unable to raise the issue of the ISPs DNS not being able to resolve some addresses.
I have discovered since my original post (using nslookup), the google DNSs are used by default by the ar300m, it is this default I need to change as it is unaffected by the DNS settings in the GUI.

To add to the original description, I discovered this problem when trying to set up a VPN using OpenVPN from the routers GUI, the address for the London server was not resolved. Using a client connected to the ar300m the address was resolved, as the client was forced by the ar300m to use the google DNSs. I connected to the root account using SSH and used the process resolveip to confirm that the ar300m was unable to resolve the name into an address, I then removed the forced DNS at the ar300m and confirmed that the client was then unable to resolve the address as it was now using the ISPs DNS, so concluded that the ar300m DNS force only applies to the clients connected to it not to the router itself.

tda2806 · 2018-06-12T11:20:08.190Z

RESOLVED

I was fooled by both the ISP’s and Google’s DNSs both not resolving the name and as a consequence assumed the value set in /etc/resolv.conf was being ignored. Changed /etc/resolv.conf to point at OpenDNS Home (208.67.222.222) and the issue was resolved.

I also started with the wrong command “resolveip” doesn’t provide DNS information and so I was spending time inferring which DNS value was being used, the command “nslookup” provides better information including the DNS server.