0

Anyone help me brother

Subject: salmankamal622@gmail.com - Issue with Public NextDNS Bypassing Custom Filtering

 

Dear NextDNS Team,

 

I’m using your custom filtering settings, and they generally work great. However, I’ve noticed a specific issue. When I use your non-customized public DNS—the one without filtering—as a custom DNS in Chrome, it ends up bypassing my private DNS filtering entirely. In other words, if I put that public NextDNS address into Chrome’s custom DNS settings, it no longer respects the filtering I’ve set up through your private DNS. Other DNS services don’t bypass like this; it’s just the public NextDNS (without customization) that does.

 

I wanted to bring this to your attention in case you might consider adding an option to prevent this kind of bypass so that the private DNS filtering remains enforced.

 

Thank you for your attention.

 

Best regards,

Salman Kamal

salmankamal622@gmail.com

1 reply

null
    • Martheen
    • 6 days ago
    • Reported - view

    Other DNS services don’t bypass like this

    I doubt it. If you enable the Bypass block it might prevent common encrypted DNS services published before 20 Jan 2023 (why that specific date? because that's the last time the encrypted DNS blocklist is updated in NextDNS dns-bypass-methods github repo), but newer ones like Surfshark DNS, DNS4EU, dnscry.pt etc would go through.

    There's also no simple way to block the NextDNS DoH domain while still using NextDNS DoH (if you use the app, it use DoH).

    Anyway this is a lost cause, if someone *wants* to get around the filter, getting a fresh DoH address is just a matter of internet search.

Login to reply

Content aside

  • 6 days agoLast active
  • 1Replies
  • 39Views
  • 2 Following