Skip to content
DnsLister Forum

Where domain hunters compare notes

Problem: AdGuard uses incorrect NextDNS profile (DOH/DOT) even with custom server

Hi,
I'm having an issue with AdGuard's DNS integration.

Even when I set up a custom NextDNS server (both DOH and DOT), AdGuard continues to use a different NextDNS profile than the one configured. The official NextDNS test (https://test.nextdns.io) always shows the fp0d191d93c76f0f62 profile, while my correct profile is c3f69b.

I've verified the following:

– Android Private DNS disabled when using AdGuard
– DOH server entered correctly: https://dns.nextdns.io/c3f69b
– AdGuard reports the address as valid
– The resolver is indeed NextDNS (Milan server)
– But the profile remains the wrong one
– If I try to enter the DOT domain (c3f69b.dns.nextdns.io), AdGuard reports it as "invalid"

It seems that AdGuard is ignoring the custom server and using an unmodifiable internal/fallback DOH endpoint.

I'd like to confirm if this is a bug and if it's possible to force the use of the correct profile.

Thank you.

Source: r/Adguard · by /u/Zyxel1983

Leave a Reply

Your email address will not be published. Required fields are marked *