0

DoT to my profile-specific hostname always routes to a different profile – not mine

DoT to my profile-specific hostname always routes to a different profile – not mine

 

Hi,

 

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

 

test.nextdns.io shows:

- status: ok

- protocol: DOT

- anycast: false

- profile: [a profile ID that is not mine]

 

What I have verified:

- Happens on all devices (Android, Windows PC)

- Private DNS on Android set to my correct [profileid].dns.nextdns.io hostname

- Testing with dns.quad9.net correctly returns "unconfigured" – router is NOT intercepting DoT traffic

- Linked IP is correctly associated with my profile

- The profile shown in the test does not appear anywhere in my account

 

Question: Could this be a server-side routing issue where NextDNS is mapping my DoT connections to the wrong profile? Has anyone seen this before?

1 reply

null
    • losnad
    • 3 hrs ago
    • Reported - view

    Yes, everyone has seen this before. The «Profile» format you get on test.nextdns.io is different than the one you have in «Setup» on my.nextdns.io, it is the same but encrypted and only NextDNS know how to translate them. This is I supposed because if a user post the result from test.nextdns.io in public that others could not use that ID/profile.

    If you get «All good» and you have logs and analytics why do you believe that your traffic is going somewhere else? 

    * You don't need to link your IP with encrypted DNS (DoH, DoT, DoQ) or even with IPv6, only with IPv4. 

Login to reply

Content aside

  • 3 hrs agoLast active
  • 1Replies
  • 10Views
  • 1 Following