0

DoH Ultralow not using profile

Screen Recording 2025-10-25 140052

When using dns.nextdns.io or ultralow.dns.nextdns.io as part of a DNS Stamp used in a UniFi Dream Machine Pro via DNS-over-HTTPS, more than half of my requests do not use the specified profile from the path.

When using anycast.dns.nextdns.io as part of the exact same stamp, all of my requests use the specified profile as part of the path.

Diag: https://nextdns.io/diag/85a76c00-b14f-11f0-b36f-012955505520

Stamp with profile removed: sdns://AgcAAAAAAAAAAAAXdWx0cmFsb3cuZG5zLm5leHRkbnMuaW8PL2FiY2RlZi9VRE0gUHJv

4 replies

null
    • R_P_M
    • 2 days ago
    • Reported - view

    Maybe it's only affecting that Melbourne PoP server. Try with dns1.nextdns.io or dns2.nextdns.io in the stamp host name, see if you can narrow it down to a single PoP server.

      • adrianmaceau
      • 2 days ago
      • Reported - view

      Good idea. Just tested this and DNS1 and DNS2 both appear to individually work correctly. The issue is only when using dns.nextdns.io or ultralow.nextdns.io.

      • R_P_M
      • 21 hrs ago
      • Reported - view

       Well that's a strange result.

      What are the DNS servers being used to resolve dns.nextdns.io and so on?

      • adrianmaceau
      • 11 hrs ago
      • Reported - view

       the DNS servers being used to resolve the DoH endpoints are my ISP's.

      dig ultralow.dns.nextdns.io @119.40.106.35 +short
steering.nextdns.io.
116.90.72.153
119.252.93.133

      Interestingly, these resolve to Adelaide IP addresses. The test.nextdns.io result ends up identical to the original video recording shared (including ultimately landing on a Melbourne endpoint, with GSL being broken).

Login to reply

Content aside

  • 10 hrs agoLast active
  • 4Replies
  • 45Views
  • 2 Following