0

Blocklist not being enforced on my PC only.

I'm experiencing an issue where domains added to my denylist and rewrite list in NextDNS are still resolving and loading normally on my PC, despite showing up in the logs. Here's what I've tried:

  1. Confirmed DNS is set correctly

  • My PC is using the correct DNS Servers via IPv4 and IPv6

  • Verified via nslookup that queries are going through dns1.nextdns.io

  •  

  • Verified NextDNS is active

    • test.nextdns.io shows "status": "ok" and my correct configuration name

    • DNS queries appear in the NextDNS logs

  1. Added domains to denylist and rewrites

    • Domains like example.com were added to the denylist to test it

    • Also added rewrites to 127.0.0.1 for the domains

    • Despite this, they still resolve to real IPs and load normally

  2. Flushed DNS cache

    • Ran ipconfig /flushdns after each change

  3. Checked browser DNS overrides

    • Disabled DNS-over-HTTPS in Chrome and Firefox

    • Ensured browsers are not bypassing system DNS

  4. Confirmed IP is linked to config

    • Used the programmatic link URL to manually link my public IP

    • Verified that my config is being used

Despite all this, denylisted domains are not being blocked on my PC. Interestingly, the same domains are blocked on my phone, which confirms that the config and denylist are functional—but something is failing on the PC side.

 

Also yes I used ai to write this as for 1 hour straight I was trying to get it to help me to fix this. Please dont judge me for that as I didnt really know what to write.

 

Regards

Firstthingsfast

2 replies

null
    • Lou_srj
    • 2 mths ago
    • Reported - view

    Did you find any solution to this? I'm facing the same issue:(

    • DeenMaster
    • 4 days ago
    • Reported - view

    1. Confirm you have only one config, or that you know which one your PC is on. Open https://my.nextdns.io and check the config list. If you have more than one, every rule you add must go to the config your PC is actually using. If a config URL redirects to a different ID after login, it isn't yours.

    2. Check which IP your PC is really resolving through. Run nslookup example.com with no server specified. If the output shows 45.90.28.30 / 45.90.30.28, you're on the generic anycast addresses and relying on IP linking. Use the config-specific addresses from your Setup page instead (they look like 45.90.28.XX / 45.90.30.XX, where XX is unique to your config). Test with nslookup example.com 45.90.28.XX ; a working config returns 0.0.0.0 and ::.

    3. On Windows 10, don't trust the Settings app to save DNS. It silently reverts. Set it via ncpa.cpl → Wi-Fi → Properties → IPv4 → Properties → Use the following DNS server addresses. Then disable/re-enable the adapter and confirm with ipconfig /all that the DNS Servers line actually shows your config's IPs.

    If DNS is confirmed working but a browser still loads the site, clear that browser's cache specifically — edge://net-internals/#dns → Clear host cache, plus Ctrl+Shift+Delete → Cached images and files.

    The fastest long-term fix is the NextDNS Windows app with your Configuration ID. It uses DoH, ignores adapter DNS entirely, and sidesteps all three issues above.

    TLDR of what the clanker said as a summary of my two-hour fight with the same issue: check control panel network connections, right click on Wi-Fi, properties, and set the IP addresses there too. Make sure NextDNS didn't randomly change them (and if it did, change it to the new ones in settings and control panel)

Login to reply

Content aside

  • 2 hrs agoLast active
  • 2Replies
  • 271Views
  • 3 Following