0

Using Chicago server and not local server.

Here is diag:

https://nextdns.io/diag/b726f660-cfe0-11eb-b69c-95e064aa8b52v

4 replies

null
    • losnad
    • 3 yrs ago
    • Reported - view

    There is a dedicated place for this:

    https://help.nextdns.io/t/y4hmvcx/report-network-latency-issue

    For some reason you added an extra letter (v) at the end of your link.

      • Bryan_Shaw
      • 3 yrs ago
      • Reported - view

      losnad just posted there. I am concerned as it doesn’t seem like the devs are responding to these issues. 

      • losnad
      • 3 yrs ago
      • Reported - view

      It is a small team. When there is a real problem they do their best to fix it.

      In the mean time, if you can edit the link of the DNS, you can try this:

      https://help.nextdns.io/t/h7hkyw2/forced-ultralowanycast

      This is how I fixed mine.

      • Bryan_Shaw
      • 3 yrs ago
      • Reported - view

      losnad Bingo. That is a great bandaid until my routing issue is fixed. I put both of those as dns servers including my ID and it is now using my local server.

Login to reply

Content aside

  • 3 yrs agoLast active
  • 4Replies
  • 125Views
  • 1 Following