1

Router in CA, USA with DoT is using NextDNS server in Sydney, Australia

Hi,

I am paying customer. My router has DOT enabled and is located in the northern California, USA area. My browser page load is extremely slow. Here are my observations:

1. Ping to the recommended NextDNS IPv4 DNS server 45.90.28.216 is 160ms.

2. dnsleaktest.com shows only one DNS server (103.1.213.21, GSL Networks, in Sydney, Australia).

3. Internet speed significantly improves when I use Cloudflare or Xfinity (ISP) servers.

Here is the NextDNS diagnostic tool output: https://nextdns.io/diag/347b0990-2469-11f0-afa7-87409dc66d44

I appreciate any input into addressing the slow network response.

10 replies

null
    • NDH
    • 3 wk ago
    • Reported - view

    Same problem here also, I'm in California.

    https://dns.nextdns.io/info

    {"locationName": "馃嚘馃嚭 Sydney, Australia", "pop": "gsl-syd", "rtt": 179245}
    • R_P_M
    • 3 wk ago
    • Reported - view

    @illustratorOne9331

    Until the routing is fixed, I would suggest you set 45.90.30.*** as the first DNS server, because anycast 1 is routing you to Australia (whereas anycast 2 is correctly routing you to a local server).

      • IllustratorOne9331
      • 3 wk ago
      • Reported - view

       Thanks for the suggestion. How would I go about doing that with DoT? I don't seem to have control over the servers DoT routes over.

      • R_P_M
      • 3 wk ago
      • Reported - view

      In your router settings, where you put 45.90.28.0 & 45.90.30.0

      simply put the 45.90.30.0 entry first. (assuming that's how you set it up in the router).

      • IllustratorOne9331
      • 3 wk ago
      • Reported - view

       Thank you, R P M!

    • NDH
    • 3 wk ago
    • Reported - view

    Anycast is such a piece of hot garbage, at least from residential ISPs that will cut costs and route you around the world to save a few bucks. Great in theory, terrible in practice.

    All these paid DNS providers should just let us point directly to DNS servers at locations of our choice (for static locations such as home routers, mobile devices sure, use anycast). How many man-hours have we wasted troubleshooting anycast and fixing routing? It breaks, it gets fixed, rinse and repeat with no end in sight.

      • IllustratorOne9331
      • 3 wk ago
      • Reported - view

       I agree! We need a fix! 160ms latency is unacceptable with current internet speeds.

    • IllustratorOne9331
    • 3 wk ago
    • Reported - view

    Here are ping times using iStat Menus. The last 4 are NextDNS servers. IPv6 servers masked for privacy.

    • NDH
    • 3 wk ago
    • Reported - view

    yeah .28 is messed up

    • NDH
    • 5 days ago
    • Reported - view

    hey @NextDNS  any plans to fix this please?

Login to reply

Content aside

  • 1 Likes
  • 5 days agoLast active
  • 10Replies
  • 170Views
  • 3 Following