0

DoH3

Please tell me. I don't know if everyone has this problem, but here's the thing. Why is it that whenever I try to open a website, the connection always drops first, and then after that, a normal request is made and the site opens. The most interesting thing is that I only see this when using the DoH3 protocol. For example, with the DoQ protocol, this has never happened. Could it be that my requests are GET/ip HTTP/2.0? 

At first, I thought it might be due to problems with a specific DNS server and changed it. But then I began to notice that it wasn't a problem with a single server. I'm experiencing (problem) this on my Samsung S20+ 5G Android smartphone.  I'm using your DNS in app AdGuard, 

 

5 replies

null
    • Adalat_Mamishov
    • 2 days ago
    • Reported - view

    one of the errors that occurs when trying to open a page. 

    • DnD
    • 14 hrs ago
    • Reported - view

    Приветствую Адалат. Вероятно вам тут никто не ответит. Попробуйте поинтересоваться на сайте Reddit, сабреддит - NextDNS

      • Adalat_Mamishov
      • 8 hrs ago
      • Reported - view

       

      Дело в том, что я покопался в сети (спрашивая у Копилот от Майкрософт), спросил у одного из сотрудников АдГуард  и решил покамест вернуться на простой DoH2. Он точно более стабилен, в сравнении с с этим DoH3. И вправду, как только я вписал просто DoH2, такие проблемы сами по себе. Видимо не все сервера, сайты покамест перешли на этот протокол. Ведь поддержка должна быть взаимной. Так что проблема решилась, вот таким образом 

    • losnad
    • 55 min ago
    • Reported - view

    I don't know what is the problem on your device but jobs.glorri.az opens just fine on me with Brave, Firefox and Web video cast. I also use AdGuard app and DoH3. And on browserleaks.com it shows the same as yours: Request GET /ip HTTP/2.0

    I did not had problems with DoH3 in AdGuard using this format: 

    h3://dns.nextdns.io/UserID/DeviceID

    Maybe you activate https filtering in AdGuard and your browser doesn't like it (some app don't work with https filtering if you don't have root). Maybe try to remove the AdGuard CA and reinstall it. 

      • Adalat_Mamishov
      • 40 min ago
      • Reported - view

        

       

      No, the problem here isn't with any one website. I just left a screenshot with a description of the error. I also experience other errors when using DoH3. I'll just emphasize that at first there's an error trying to establish a connection, and then the site opens quickly and normally. My internet provider doesn't block any websites.  

       

      Here, for example, is another error that I noticed  (attention to photo)+ another one error- DNS_PROBE_FINISHED_NXDOMAIN

      These errors not occur if I use simple DoH2, without h3://, i.e. https://. 

Login to reply

Content aside

  • 40 min agoLast active
  • 5Replies
  • 50Views
  • 2 Following