Understand How DNS Filtering Works
DNS stands for Domain Name System — the system that translates domain names likegoguardian.com into IP addresses. GoGuardian DNS intercepts these translation requests and applies your filtering policy before any device can reach a blocked domain.
Because filtering happens at the network level, GoGuardian DNS:
- Covers all devices connected to your filtered networks, regardless of operating system or browser
- Requires no software installation or agent deployment on individual devices
- Applies the same filtering rules to managed and unmanaged devices on the same network
If a blocked site uses HTTPS, the browser may display a “Your connection is not private” warning. This is expected behavior. The warning appears because the requested certificate (for the blocked site) does not match the certificate from GoGuardian’s block page redirect.
Understand What GoGuardian DNS Filters
GoGuardian DNS applies filtering at the domain level. It uses the same policy framework as GoGuardian Admin, with important differences:
URL path filtering example: A policy rule that blocks
sites.google.com/unblockedgames targets the path /unblockedgames. GoGuardian DNS ignores the path and would need to block the entire sites.google.com domain to enforce that rule — which would block all of Google Sites. For path-level rules, use GoGuardian Admin filtering.
Wildcard filtering: Wildcards like *unblock* match domains and subdomains — for example, unblockedgames.com. They do not match URL paths.
Districts that deploy DNS Precision Filtering get per-student reporting and per-student filtering with GoGuardian DNS, instead of the network-level-only behavior described above. Contact your GoGuardian Account Manager to learn whether DNS Precision Filtering is available for your deployment.
Understand When to Use GoGuardian DNS
Use GoGuardian DNS when you need:- Filtering for BYOD, guest, or unmanaged devices on campus
- A network-level filtering layer that works regardless of browser or operating system
- A supplement to GoGuardian Admin that extends coverage beyond managed Chrome devices
Fix a Site That Is Still Blocked After You Allow It
If GoGuardian DNS still blocks a site after you add an allow rule, check the following:- Go to GoGuardian Admin and select DNS Traffic. Select All Networks, select the DNS Network, and enter the blocked domain in the Recent Activity Search search field. DNS Traffic shows data only when Logs and Statistics is turned on for the network.
- If your allow rule includes a URL path, such as
sites.google.com/approved, GoGuardian DNS ignores the path. Allow the domain instead. - A page can load resources from other domains, such as content delivery networks. If DNS Traffic shows another domain blocked when the page loads, add an allowed Website URL rule for that domain.
- Confirm the allow rule is in the policy assigned to that network. Go to Filtering > DNS Networks to review the policy assigned to each network.