No Data Available — DNS Inactive

If your CleanBrowsing dashboard shows "No Data Available" or "DNS Inactive," your devices aren't sending DNS queries through CleanBrowsing yet. Here's how to fix it.

Step 1: What "No Data Available" Means

When your CleanBrowsing dashboard shows "No Data Available" or "DNS Inactive," it means CleanBrowsing hasn't received any DNS queries from your network or devices recently.

This typically means one of three things:

  • Your devices aren't configured to use CleanBrowsing DNS servers
  • Your public IP address hasn't been registered in your CleanBrowsing account
  • Something on your network is overriding your DNS settings (router, ISP, or security software)

Step 2: Verify Your DNS Settings

Confirm that your device or router is using CleanBrowsing DNS servers. The easiest way is to use terminal/command prompt:

On Windows

nslookup cleanbrowsing.org

The "Server" line should show one of CleanBrowsing's DNS IPs (e.g., 185.228.168.168 for the Family filter).

On macOS / Linux

dig cleanbrowsing.org

Check the ;; SERVER: line in the output. It should point to a CleanBrowsing IP.

If the DNS server shown is not a CleanBrowsing IP, your device isn't configured correctly. Visit the Setup Guide for step-by-step instructions.

Step 3: Check Your Public IP

For paid accounts, CleanBrowsing needs your public IP address registered in the dashboard to associate DNS queries with your account.

  1. Visit my.cleanbrowsing.org and log in
  2. Go to Your NetworkNetwork IPs
  3. Compare the IP listed with your actual public IP (check at whatismyip.cleanbrowsing.org)
  4. If they don't match, update your IP in the dashboard

If your public IP changes frequently (common with residential ISPs), set up a dynamic IP updater to keep it current.

Step 4: Flush Your DNS Cache

After making DNS changes, your device may still use cached entries from the previous DNS server. Flush the cache:

Windows

ipconfig /flushdns

macOS

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux

sudo systemd-resolve --flush-caches

Also clear your browser's DNS cache — browsers maintain their own cache separate from the OS.

Step 5: Test DNS Resolution

Verify that CleanBrowsing is actively filtering by testing a known-blocked domain:

nslookup pornhub.com

If CleanBrowsing is working correctly with the Family or Adult filter, this should return a blocked IP (like 0.0.0.0 or CleanBrowsing's block page IP). If it returns a real IP address, DNS filtering isn't active.

You can also use the command-line DNS tools guide for more detailed diagnostics.

Step 6: Common Causes

If DNS is still showing as inactive after the steps above, check for these common issues:

ISP or Router Overriding DNS

Some ISPs and routers force their own DNS servers regardless of your settings. Check if your router has a DNS override enabled. See how to block DNS bypasses with firewall rules.

Security Software Conflicts

Antivirus or security software (like Avast or Norton) may redirect DNS queries to their own servers. See known services that conflict with CleanBrowsing.

VPN or Encrypted DNS

If a VPN is active, it typically uses its own DNS servers, bypassing CleanBrowsing entirely. The same applies to browser-level encrypted DNS (DoH). See how to prevent filter bypass.

CGNAT (Carrier-Grade NAT)

If your ISP uses CGNAT (common with T-Mobile and some cable providers), multiple customers share the same public IP. This can cause issues with IP-based account association. See understanding CGNAT.

Still stuck?

Contact support@cleanbrowsing.org with your public IP address and a screenshot of your DNS settings. We'll help you get connected.

Related Guides

Setup Guide

Step-by-step instructions for configuring CleanBrowsing on any device or router.

Dynamic IP Updater

Keep your public IP current in CleanBrowsing when it changes.

Command-Line DNS Tools

Use dig, nslookup, and other CLI tools to diagnose DNS issues.