Query Refused until I change DNS back and forth

[TomBowyer]

Hi All,
I have a frustrating issue, can anyone help please - i've got an AC87U running 380.69_2 (although this issue has been here for 2+ years). I use the router for WiFi and as an internal DNS/DHCP server (but no WAN connectivity as I have a separate broadband router). The DNS forwards to 8.8.8.8.

The routers DNS works fine normally, except when it gets powered off/rebooted the DNS stops working (nslookup just returns "query refused"). To resolve the issue I have to change the DNS Server 1 from it's correct value (10.10.10.3 which is the routers own address) to something else random (e.g 8.8.8.8) and then change it back to 10.10.10.3 again. This seems to kick it in to life.

Any idea why I need to do this, do I have a config issue?

Settings are:

AC87U Routers Address: 10.10.10.3
ADSL Router Address: 10.10.10.2
IP Pool Starting Address: 10.10.10.100
IP Pool Ending Address: 10.10.10.200
Lease Time: 86400
Default Gateway: 10.10.10.2
DNS Server 1: 10.10.10.3
Advertise router's IP in addition to user-specified DNS: No
Forward local domain queries to upstream DNS: No
Enable DNSSEC support No

Any ideas?
Thanks!
Tom.

 

[ColinTaylor]

My guess is that dnsmasq doesn't compete its initial setup because you don't have a working WAN connection. Changing the LAN settings forces dnsmasq to start up. What have you set "WAN Connection Type" and "WAN DNS Setting" to?

 

[TomBowyer]

Hi,

My guess is that dnsmasq doesn't compete its initial setup because you don't have a working WAN connection. Changing the LAN settings forces dnsmasq to start up. What have you set "WAN Connection Type" and "WAN DNS Setting" to?

Thanks, interesting idea, does the below provide any insight?

Wan Connection Type = Automatic IP
Enable WAN: No
Enable NAT: No
Wan DNS Setting
Connect to DNS Server Automatically: No
DNS Server 1: 8.8.8.8
DNS Server 2: 8.8.4.4

I assumed that by setting "Enable WAN" to no this entire section gets missed?


Tom.

 

[ColinTaylor]

I assumed that by setting "Enable WAN" to no this entire section gets missed?

I would have thought the same. (Likewise the NAT setting should be irrelevant but personally I'd set it to "Yes" in case you ever go back to using the router "normally".)

Have a look in the router's syslog after the router has been rebooted. You might have to increase the log levels, I can't remember. Look for messages from dnsmasq to see if it's not starting up (or constantly restarting) properly.