3 ms·
Somewhat related. If I use DNS-over-HTTPS with a nextdns edge server the response time is of the order of 10ms. With google 8.8.8.8 or nextdns 45.90.* it's abou
by msravi 5y ago
Somewhat related. If I use DNS-over-HTTPS with a nextdns edge server the response time is of the order of 10ms. With google 8.8.8.8 or nextdns 45.90.* it's about 130-140ms. Ever since I set up a local pihole with nextdns DoH as the upstream server, things have been very spiffy. The pihole cache also helps with sub-ms response times, especially if you set a minimum ttl of 40 mins or so.
- lordnacho 5y agoI have a PiHole. How do I configure DoH?
- msravi 5y agoUse cloudflare/nextdns DoH clients and set them to listen on some other port (like 5053/5153). Point the pihole "custom" upstream servers to 127.0.0.1#5053 and/or 127.0.0.1#5153 https://docs.pi-hole.net/guides/dns/cloudflared/ https://docs.pi-hole.net/guides/dns/cloudflared/
- NavinF 5y ago130-140ms!? That’s very unusual. Can you reproduce that latency with UDP ping to a cloud VM or a DNS request to a cloud VM? Maybe your router or ISP is messing with UDP or intercepting DNS and forcing you to use their DNS servers. Lots of “firewall” middleboxes do that by default. Or maybe there’s an path MTU issue that triggers retransmit on every UDP packet, but not on an established TCP connection that has learned the correct MTU.