0

This device is currently using ”Google DNS” as DNS resolver

Need help troubleshooting this error. It’s starting to appear across all of our NextDNS sites.

This device is not using NextDNS.

This device is currently using ”Google DNS” as DNS resolver.

This is new behavior; we’ve had NextDNS running for years without this issue. We’re using a UDM Pro with static DNS set in the DHCP scope, and we’ve confirmed that devices are receiving the NextDNS DNS servers. We’ve also confirmed all linked IPs are correct.

We can see the traffic in the NextDNS logs, but computers are still able to access sites that should be blocked.

2 replies

null
    • R_P_M
    • 18 hrs ago
    • Reported - view

    Check browser settings for anything DNS related, maybe secure DNS is on auto or something. 

    • jroks123
    • 6 hrs ago
    • Reported - view

    RPM is likely on the right track here. What you’re describing sounds like some devices/browsers are bypassing the OS/router DNS settings and using their own Secure DNS/DoH resolver instead (often Google DNS by default).

    That would explain why:

    • devices are still receiving NextDNS via DHCP

    • you still see traffic in NextDNS logs

    • but some blocked sites still resolve successfully

    • and NextDNS reports “This device is currently using Google DNS”

    Modern browsers (Chrome, Edge, Firefox) and some operating systems can automatically enable Secure DNS/DoH and silently use external resolvers independent of the network DNS settings.

    Things I would check:

    • Chrome/Edge → Settings → Privacy & Security → Use Secure DNS
    • Firefox → DNS over HTTPS
    • Android Private DNS settings
    • Endpoint security software/VPN clients that may force their own DNS
    • Any browser signed into Google accounts with synced Secure DNS settings

    This is becoming more common because browsers increasingly treat network DNS as optional if Secure DNS is enabled.

Login to reply

Content aside

  • 6 hrs agoLast active
  • 2Replies
  • 37Views
  • 3 Following