2

DNS over QUIC doesn't work anymore

Hi. 

It seems that QUIC isn't working anymore. 

quic://iPhone-XXXX.dns.nextdns.io:8853

quic://iPhone.XXXX.dns.nextdns.io:8853

Any idea what's wrong?

20 replies

null
    • Ruby_Balloon
    • 2 yrs ago
    • Reported - view

    have you tried removing the port at the end?

    • Pierre_Cartier
    • 2 yrs ago
    • Reported - view

    @nisten

    Greg, you do realize that I had no issue before? FYI you should know, if you tried, that it does not work because it is not the right set up.

    Also, there is an issue with QUIC as it is well documented on the web. Many people are complaining about it since a week now.

    I just switched to DoT until NextDNS guys solve the problem.

    • Aidan_Gee
    • 2 yrs ago
    • Reported - view

    Same issue for me too. I read somewhere it’s because DoQ has now become an official standard and there are some backwards compatibility issues that NextDNS need to implement (Which is why AdGuard DNS quic works but NextDNS no longer does).

    • NextDNs
    • 2 yrs ago
    • Reported - view

    Make sure you remove the custom port.

      • Aidan_Gee
      • 2 yrs ago
      • Reported - view

      NextDNS unfortunately it no longer works, even without the port number added. It used to work however it appears to have stopped in the last week or so.

    • Chris_Leidich
    • 2 yrs ago
    • Reported - view

    I’m having the same issue, and also started noticing it in the past 3-5 days. No custom port. I’m wondering if the changes made to support the final DoQ spec server side are related, but have no way of confirming that. I’m willing to help test if needed. 

    • NextDNs
    • 2 yrs ago
    • Reported - view

    We switched the server to the final implementation of DoQ and the new official port. It should work with an up-to-date version of a DoQ client with no custom port provided.

      • Chris_Leidich
      • 2 yrs ago
      • Reported - view

      NextDNS I am wondering if the DoQ implementation in the AdGuard mobile apps is out of date now. I know they updated their servers and AdGuard _Home_ to use the latest spec, but the iOS app is a month old, might be using an older version. Wonder if that's the missing piece.

      • Leonard
      • 2 yrs ago
      • Reported - view

      Chris Leidich Yes, you need to wait AdGuard Team to update their APP, or you can open the new issue here !

      • Pierre_Cartier
      • 2 yrs ago
      • Reported - view

      NextDNS 

      Did you try what you are suggesting?

      You do realize that no one can get it working with or without the port.

      People are also complaining about this problem on Reddit. You might want to check why it is not working. 

      • NextDNs
      • 2 yrs ago
      • Reported - view

      Pierre Cartier try forcing the port to 853, seems like the AdGuard iOS application still have an old version of DoQ with the old standard port.

      • Pierre_Cartier
      • 2 yrs ago
      • Reported - view

      NextDNS Port 853 works. Cheers. 

      BTW DoH3 disappeared...

      • Chris_Leidich
      • 2 yrs ago
      • Reported - view

      NextDNS This works for me too - thanks!

    • gorilla_p
    • 2 yrs ago
    • Reported - view

    Can confirm, DoQ stopped resolving about 2 weeks ago in the middle of the day. Switched to DoH and working normally.

    Not working for me via Adguard Home. Seeing reports of iOS users with same issue.

      • Pierre_Cartier
      • 2 yrs ago
      • Reported - view

      Ryan Likewise 

      • Patrik_Kro
      • 2 yrs ago
      • Reported - view

      Ryan DoQ to NextDNS servers is working again with AdGuard Home. NextDNS developers have updated the servers.

      • Pierre_Cartier
      • 2 yrs ago
      • Reported - view

      Patrik Kro As mentioned on the other post only with port 853 vs 8853

    • Aidan_Gee
    • 2 yrs ago
    • Reported - view

    Official response by AdGuard here:

    "AdGuard DoQ protocols will be changed to the new version in the next update. The best solution right now is to force port 853 manually."

    • gorilla_p
    • 2 yrs ago
    • Reported - view

    It appears to be working with AdGuard now. Something to note that took me a minute.

    When inserting the DNS server, my keyboard capitalizes the first letter.

    If I entered Quic:// upstream test would fail.

    If I enteted quic:// upstream test was successful.

    It appears to be case sensitive.

    • Pierre_Cartier
    • 2 yrs ago
    • Reported - view

    Again it doesn't work. Is NextDNS or AdGuard responsible for it?

Login to reply

Content aside

  • 2 Likes
  • 2 yrs agoLast active
  • 20Replies
  • 1851Views
  • 7 Following