There is an another way to change DNS using Chrome (by going to privacy and security settings)
Suppose i have setup DNS on my phone but also did setup using chrome's DNS then next DNS doesn't work on Chrome (don't know about other browsers)
Please Fix this issue
I know it's going to take a lot of time till then could you suggest any steps to prevent this
What in the replies are true"just when private dns is not off"
But nextdns have this issue for a long time.
You can test this using this method:
1. Install "intra" app.
2. Set your nextdns DoH address in it and turn it on.
3. Then set another DoH (another profile that you have created for your browser or maybe same profile that you have set in the intra app)
Then chrome/Firefox/etc can't browse any other websites.
Seems like nextdns banned using its dns on multiple levels (router > OS > browser)
These options won't get in conflict with each other.
Just private dns on Android 10+ will get in conflict with other dns that you will set in android because it will replace those. (Google internally did this (to maybe avoid dns leaks or such))
But using nextdns on vpn (or something like intra) and then using it in browser because you have set up different settings for each one and created different profiles with different settings in you account for each usage (OS, Browser, Router, etc)
This behavior won't get into any conflict.
You can test it by changing one of the dns resolvers to any other public resolver that exist.
But we don't want to do that.
We want to get layered protection for each level of our usage and unfortunately nextdns have bug or intentionally blocked this (i can't understand why if they did this intentionally though)
P.S: my similar issue in another bug report that i created today before i have seen this:
I'm using the same Config on my router, as Private DNS and on Chrome, did this to test and everything is perfectly fine.
The issue might be with that Android version by the manufacturer as some change things and lastly it could also be something to do with DoT being blocked in the case of Private DNS as it's simple to block by ISP/Firewalls.
Wanted to let everyone know that on Android 12 it works perfectly fine on my end, but using my carrier that blocks DoT it doesn't function when Private DNS is on as stated by others.
From what I've gathered they aren't blocking anyone from using it on multiple layers, either the ISP or Device/OS is doing something wrong to somehow break the chain.