Question NextDNS setups

Please provide comments and solutions that are helpful to the author of this topic.
When "Private DNS" is on "ON" (not the custom provider option), what secure DNS does the phone use for phone and Wi-Fi networks?
Cannot get the point; I use custom provider in phone private dns to bypass the dns provider in modem router settings.
 
When "Private DNS" is on "ON" (not the custom provider option), what secure DNS does the phone use for phone and Wi-Fi networks?
When the Private DNS setting is set to "Automatic" in Android the device attempts to use DNS over TLS (DoT) if the network’s DNS server supports it. If the network’s DNS server (typically provided by the ISP or router via DHCP) supports DoT, Android will encrypt DNS queries to that server. If DoT is not supported, the device falls back to unencrypted DNS queries (UDP on port 53). This mode relies on the network’s DNS configuration and does not explicitly specify a private DNS provider. But Some Android device manufacturers (e.g., Samsung, Google Pixel) or carriers may preconfigure a default Private DNS provider in the "Private DNS provider hostname" setting. For instance, Google Pixel devices may default to "dns.google" when Private DNS is set to "On," but this is not guaranteed across all devices. Most stock Android implementations leave the hostname field blank unless manually set by the user. If you want encrypted dns ( DOT) you should use the "custom provider" option and not the "Automatic" or "ON" option.
 
Last edited:
Does Android fall back to the default DNS if the custom DNS provider is unreachable?
I am not sure; I believe you have to manually disable private dns in android to rely back on modem router dns settings.
 
Does Android fall back to the default DNS if the custom DNS provider is unreachable?
If you've taken the step to manually configure a Private DNS provider hostname on your Android device (like dns.google), the system will prioritize a secure DNS over TLS (DoT) connection to that exact server. If this secure connection can't be established, Android will "fail hard." This means it won't fall back to an unencrypted DNS or seek out another DNS server. This strict approach is a privacy measure, designed to prevent situations where an attacker could force your device to use an insecure DNS.
 
This strict approach is a privacy measure, designed to prevent situations where an attacker could force your device to use an insecure DNS.
Does iPadOS fall back to the default DNS if it is using a configuration profile and the DNS provider is unreachable?
 
Does iPadOS fall back to the default DNS if it is using a configuration profile and the DNS provider is unreachable?
If you configure DNS via a configuration profile on iPadOS, especially for encrypted DNS (DoH/DoT), the device will typically not automatically fall back to unencrypted, network-provided DNS if the configured servers become unreachable. Instead, it prioritizes the profile's settings, which can lead to connectivity issues unless you manually intervene or the profile has specific exceptions for certain networks/domains (like captive portals).
 
Available for use at the browser level?
No, you would need to use a separate app on the device or the network like AdGuard Home, Yogadns and similar things for DoH/3 or DoQ.
If you've taken the step to manually configure a Private DNS provider hostname on your Android device (like dns.google), the system will prioritize a secure DNS over TLS (DoT) connection to that exact server. If this secure connection can't be established, Android will "fail hard." This means it won't fall back to an unencrypted DNS or seek out another DNS server. This strict approach is a privacy measure, designed to prevent situations where an attacker could force your device to use an insecure DNS.
Apparently since Android 11, if you use Google or Cloudflare as the Private DNS provider, then they use DoH/3 instead of DoT. For any other provider DoT is used.
 
I do find it a bit of housekeeping in using NextDNS as far as what it is blocking in regard to this Mullvad example (I'm only using the HaGeZi - Multi PRO++ blocklist).
From a Google search of the blocked connection, which I added to the Allowlist.
ipv4.am.i.mullvad.net is a domain name associated with the Mullvad VPN service. Specifically, it is used by the Mullvad VPN application to check if a user's device is connected to the VPN and to verify DNS leaks. The domain allows the Mullvad app to confirm that it is correctly routing traffic through the VPN.

But, I also found this interesting in keeping track of some of the Avast (AVG free antivirus) blocked connections in that my AVG UI, no longer shows the scare banners or suggestions at the bottom. It's been a very clean UI, unless it's taking a time out and will eventually pop up? I've run some Smart Scan with the usual prompts of "needing to or having to resolve issues", but after exiting out of those, there have been no UI notices, even after 3 PC restarts and AVG updates? Everything seems to be functioning normally.

Pre NextDNS router configured/Linked IP.
avg scare tatics.jpg

Post NextDNS after about 6 days.
nextdns avg.jpg
 
Last edited:
I do find it a bit of housekeeping in using NextDNS as far as what it is blocking in regard to this Mullvad example (I'm only using the HaGeZi - Multi PRO++ blocklist).
From a Google search of the blocked connection, which I added to the Allowlist.


But, I also found this interesting in keeping track of some of the Avast (AVG free antivirus) blocked connections in that my AVG UI, no longer shows the scare banners or suggestions at the bottom. It's been a very clean UI, unless it's taking a time out and will eventually pop up? I've run some Smart Scan with the usual prompts of "needing to or having to resolve issues", but after exiting out of those, there have been no UI notices, even after 3 PC restarts and AVG updates? Everything seems to be functioning normally.

Pre NextDNS router configured/Linked IP.
View attachment 289398

Post NextDNS after about 6 days.
View attachment 289399
You may get the same output with blocking avasui.exe/avgui.exe using firewall.
 
@Jonny Quest Are you sure it was blocked by Hagezi Multi Pro++? It's not blocked for me.
I happened to have enable Block Bypass Methods, which explicitly states that it includes VPNs. I just saw it being blocked and allowed it, I should have highlighted that entry to see the notification of what blocked it. Learning curve thing on my part :eek: :)

Being able to filter the Logs list by Blocked Queries Only, comes in handy.
 
Last edited:
For blocked sites (or parental control) in NextDNS, do you whitelist the root or subdomain?
 
For blocked sites (or parental control) in NextDNS, do you whitelist the root or subdomain?
That depends whether you just want to quickly allow the service or get more granular control. For example, I allow 5 subdomains for mail.ru and that blocks the rest used for ads, social, etc.

capture_07152025_180541.jpg
 

You may also like...