As soon as possible solved brother

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!