GoGuardian DNS resolvers are not responding when traffic from your network is not reaching GoGuardian’s DNS servers. This means filtering is not active for that network.
Identify Possible Causes
- The network’s public IP address has not been added in GoGuardian Admin
- DNS traffic has not been redirected to GoGuardian’s resolver addresses
- A firewall or network filter is blocking traffic to GoGuardian’s DNS servers
- The public IP address in GoGuardian Admin does not match the current public IP of the network
Apply a Solution
-
Confirm the network’s public IP address is entered in GoGuardian Admin under Filtering → DNS Networks. If it is missing or incorrect, update it and save.
-
Confirm your network’s DNS traffic is pointing to GoGuardian’s resolver addresses. Find the device that manages public DNS settings — typically a firewall, router, or DHCP server — and verify the following addresses are configured:
-
Test connectivity to each resolver using the terminal command:
Replace
[resolver IP] with each resolver address. A response confirms connectivity. No response indicates the resolver is unreachable from your network.
-
If connectivity tests fail, check your firewall and network filters to confirm that incoming and outgoing traffic to GoGuardian’s resolver addresses is permitted.
If none of the above resolved the issue, contact GoGuardian Support with the results of your nslookup tests and your network’s public IP address.
Resources
Last modified on July 9, 2026