0

Using router as DNS results in query failure

I configured my home DHCP to use my ASUS router as the DNS server, and the router pointed to NextDNS upstream. This configuration works for about an hour or so before failing to serve all queries. Even my.nextdns.io and help.nextdns.io fail to resolve. I’ve ruled out any security control settings by turning them all off.

I’m currently attempting to work around this by publishing the NextDNS server via DHCP directly, however this is less than ideal for my home network. My router knows the names of devices that are local to my network.

3 replies

null
    • R_P_M
    • 9 mths ago
    • Reported - view

    You could try setting the DHCP for both the router and one of the NextDNS servers. Devices might then switch to the NextDNS one if the router stops responding to dns requests. 

    There must be something going wrong with the ASUS router, it really shouldn’t be failing with something as simple as dns lookups. 

      • Djatah
      • 9 mths ago
      • Reported - view

       I’ll keep that in mind. For now I’ve been using rewrites for the few machines that I actually care about. Relying on resolver failover as you describe could potentially lead to a massive delay in the initial lookup, and rely on cached entries from there on. It would repeat once the cache entry expires.

      • R_P_M
      • 9 mths ago
      • Reported - view

       Potentially yes it could lead to delays but in practice most devices will switch to the other dns ip address quite quickly and will use that one exclusively, until the first dns starts to respond again. 

Login to reply

Content aside

  • 9 mths agoLast active
  • 3Replies
  • 104Views
  • 3 Following