Partner control browser custom DNS bypass private DNS only next DNS
Dear NextDNS Support Team,
My account salmankamal622@gmail.com
I’m using NextDNS’s private DNS setup on my Android device, and for the most part, it’s working well at the system level.
However, there’s a specific issue we’re encountering: in browsers like Chrome that allow setting a custom DNS within the app, if we use the public, non-customized version of NextDNS there (the one without any filtering or custom blocklists), it ends up bypassing the system-level private DNS setting. In other words, when that public NextDNS server is set in Chrome, the system’s private DNS gets overridden. Interestingly, this doesn’t happen if we set other DNS providers like family dns—only the plain public NextDNS instance causes this behavior.
We’d like to know if there’s any specific configuration or advice you can provide so that the private DNS setting always takes priority and we can avoid this bypass scenario.
Thank you very much!
1 reply
-
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
salmankamal6
Content aside
-
1
Votes
- 11 hrs agoLast active
- 1Replies
- 26Views
-
1
Following