0

DoT profile routing issue – connections assigned to wrong profile

Hi,

I am experiencing an issue where DNS-over-TLS connections to my profile-specific hostname are consistently being assigned to a different profile that does not belong to my account.

Symptoms:

test.nextdns.io returns status: ok but with a wrong profile ID
Protocol: DOT,

anycast: false

Affects all devices on my network (Android, Windows)

Private DNS on Android is set to my correct profile hostname

What I have ruled out:

Router is not intercepting DoT traffic (verified by testing with dns.quad9.net, which correctly returns unconfigured)

Linked IP is correctly associated with my profile
The wrong profile ID does not appear anywhere in my account

Request:
Could you please check server-side why DoT connections from my IP are being routed to a different profile instead of my own?

I can provide my account email, profile ID, public IP, and full test.nextdns.io output on request or via secure channel.

Thank you.

Reply

null

Content aside

  • 2 wk agoLast active
  • 22Views
  • 1 Following