0

Thousands of a.root-servers.net queries from the router

Hello Team,

First of all I am extremely impressed the features that NextDNS is offering at a very reasonable price. Hats off!

However, I would like your little help in solving a problem that I have with the NextDNS setup. From the day I decided and setup NextDNS at router level ( TP-link XC220-G3v, stock firmware, NextDNS via linked IP), I am seeing a tremendous amount (several thousands a day) of queries being sent to a.root-servers.net, almost every second which is really frustrating. This totally breaks the point of logging and alters the view of logs and analytics that I would like to have. I have confirmed by running NextDNS at device level that the queries are being generated by the router itself. 

Please help me out.

Would be happy to share additional details if asked. 

3 replies

null
    • R_P_M
    • 2 yrs ago
    • Reported - view

    TP-link (and probably other routers) are using that domain lookup to test it’s connectivity.

    To reduce that, do not set the IPv4 addresses on the wan settings, move them to the DHCP settings side. 

      • Al_Musavvir_Siddiqui
      • 2 yrs ago
      • Reported - view

       Thanks for the suggestion, YES! Moving DNS addresses to DHCP to works!

      Have disabled custom DNS in wan settings and moved nextdns addresses to DHCP section. Now works good. 

      Thanks 👍

    • Pucchi
    • 3 days ago
    • Reported - view

    I tried the same solution described here, but it does not work on my Archer AX73 V2.

    My setup is:

    • Archer AX73 V2

    • Firmware 1.3.1 Build 20260430

    • WAN DNS: 1.1.1.1 / 8.8.8.8 or 100.100.1.1 / 100.100.0.1

    • DHCP DNS: NextDNS

    Despite moving NextDNS from WAN DNS to DHCP, the router continues generating frequent a.root-servers.net queries, which are still counted by NextDNS.

    I also confirmed that these queries come from the router itself (they appear under my public IP and have no client/device identifier).

    Has anyone with an AX73 or similar TP-Link router experienced the same behavior and found a way to actually disable or bypass this connectivity check?

Login to reply

Content aside

  • 50 min agoLast active
  • 3Replies
  • 752Views
  • 4 Following