0

DOH vs DOT

Hi, I am constantly monitoring this when I encountered a constant slow down.

And somehow I arrived at checking the settings. It seems that DoT is slower compared to DoH from where I am located. I am from PH and this is an issue since it was thought that DoT would be somehow supposed to be faster but it seems it's the other way around when using NextDNS. What is wrong here? is this because DoT is newer implementation and is not yet ripe?

I have a settings in my router/mobile as DoT from which I compared my tests. Also it seems slower in android. In my mac I have the option to use the app and it was faster but it was configured as DoH. Checking from test.nextdns.io.

I might be forced to switch providers if this is not fixed. Any tips would be appreciated.

4 replies

null
    • Martheen
    • 1 yr ago
    • Reported - view

    DoT use its own port (853) that your ISP might decide to throttle for whatever reason, while DoH is just regular HTTPS on port 443 like any other web traffic.

    You can benchmark it yourself with https://github.com/ameshkov/godnsbench, also verify with https://github.com/ameshkov/dnslookup if you actually get the same name resolution on DoH vs DoT (just in case you somehow get a different resolution when one of them isn't in your ISP CDN).

    If NextDNS DoT is indeed slower in your ISP, try comparing the result from other providers (Google, Cloudflare, Quad9, AdGuard) to see if DoT is consistently slower, in which case switching to other providers won't help.

    • nferocious76
    • 1 yr ago
    • Reported - view

    Thanks. I'll look into it again.

    • Michael_Budow
    • 1 yr ago
    • Reported - view

    Have been using NextDNS and testing it with multiple different providers for the past 3 months. No issues whatsoever with any of them so far (PLDT, Converge, Globe, etc.).

    Even for enterprise level setups, NextDNS is handling traffic of multiple devices just fine. I know it might sound repetitive, but try to check your cables if you're using anything below the CAT 5E spec or if your router or devices have other network settings that could be causing a loop throttling your own speeds besides the usual PLDT network throttling.

    (If you're connecting via WiFi, then try to check the speed issue by moving a connected device back and forth from where it originally was until you're right next to the router to make sure that it's just a coverage issue.)

    As an alternative (as suggested by @martheen), you could try using Quad9 servers (most recommended) or Google servers and see if that quickly fixes your speed issues. If not, then through the process of elimination, it's not the DNS services that is the problem, it might be your physical network setup.

    Side note: If you haven't already, you might want to buy a better router (either ASUS or TPLink) if you're just directly connecting your devices to the ISP's provided modem. Those modems suck and will not do much if you're using any cable that is below the CAT 5E spec (for wired setups) and will most definitely suck if you're on WiFi (for wireless setups).

      • nferocious76
      • 1 yr ago
      • Reported - view

      Michael Budow well, thanks for the tips. but I don't really fall on those setup category. It's is really fine in my overall setup. just most of the time the ping from ping.nextdns.io go to <100ms with the stable ping at 43ms and that's it. There's no problem when I am using iphones, mac and pc. in my s23u most of the time it lags on loading. I can't actually find the culprit. but the ping does not change whether I am on the other devices. I am currently using adguard dns on my s23u and so far I have no problem (I am still testing this) I am not sure whether it was because of quic/dot vs doh config on nextdns but that's it. It's like what @martheen mentioned. It could also be the server of nextdns that lags with too many users and server location. Not too sure, but it could be that adguarddns 2.0 has a better implementation on this regard (I am not checking and comparing their codes). I used NextDNS before even adguarddns 2.0 goes to beta if that could help prove my observation. Again thanks.

Login to reply

Content aside

  • 1 yr agoLast active
  • 4Replies
  • 576Views
  • 3 Following