2

Short-term outages with DoT

I have set up the "DNS-over-TLS/QUIC" address in my Android smartphone as "private DNS" and also in the router for the home network. Basically, the service works very well, but several times a day I have short-term outages of up to 30 seconds on all end devices, both at home and mobile, during which no address can be resolved.

The problem apparently only occurs with the natively supported protocol DoT. If I only enter the unencrypted IPv6 DNS server in the router, I cannot determine any comparable failures so far.

https://nextdns.io/diag/6bddc480-68e8-11ec-987f-9119e8b922f7

29 replies

null
    • Balan_Cosmin
    • 2 yrs ago
    • Reported - view

    I need some help please

    https://help.nextdns.io/t/q6hjt2p/nextdns-not-working-through-wireguard-vpn-server

    • BCook
    • 2 yrs ago
    • Reported - view

    Using AdGuardHome and forwarding upstream to the dot://url or doh://url and then checking the hit counter in NextDNS Analytics.. I found that doh was (almost) 3x used than dot.

     

    Unbound and Core can use dot as a recursive forward.. and dnscrypt-proxy can only do doh

     

    I've used clash (proxy) which can support dot doh directly.. but I have way to prove how it's goes from one to the other..   I was also trying to name the nextdns-cli to see how that appears in the logs.. but it seems to just come from the ip address of the wan connection it is coming from.. 

    I can't seem to name that endpoint like you can with dot://dot-custom-name-123abc.dns.nextdns.io or doh://dns.nextdns.io/123abc/doh-custom-name

     

    I'm not sure if AdGuardHome had problems with dot and that is why the count was uneven.. 

     

    My 0.02

    • Techno
    • 2 yrs ago
    • Reported - view

    Same issue here with DNS over TLS. 

    I have an Asus router with NextDNS TLS address input manually. Either it stops working on a reboot or the connection just drops randomly. I also ditched the cli client as that wouldn't reconnect on a reboot

    • Andrew_Paolucci
    • 2 yrs ago
    • Reported - view

    I just started encountering issues today with DoH failing only for v4, v6 is still resolving fine and I see it in my NextDNS logs, yet I am getting no return on v4 addresses, I needed to fallback to Cloudflare for v4 but have continued testing with the NextDNS DoH v4 issues.

    Were any changes made today? Or could this be my ISP doing some form of DPI that is messing with my encrypted DNS?

Login to reply

Content aside

  • Status Fixed
  • 2 Likes
  • 2 yrs agoLast active
  • 29Replies
  • 1092Views
  • 12 Following