CLI app choosing slower endpoint. Can it be overridden?
It seems that the CLI client is choosing low latency servers in Dallas while the Anycast servers in SJC are faster. I am using CLI program on Ubuntu and MacOS systems and get the same results.
I don't know if it is geolocating me in Dallas because my ISP (Lumen/Level 3) is located there?
My question is: Is there a way to force the CLI client to choose Anycast over ULL servers? Or how can I get it to choose closer/faster servers?
Diagnostic results:
https://nextdns.io/diag/e30d3800-fe17-11ec-bf23-09ff0d59f5bd
Here are the quick test results:
Here you can see the CLI initial log results after a restart and it confirms that the Anycast server is 1ms, but it appears to connect to Dallas(dal) which is 40ms.
2 replies
-
I see that there were requests for this on the github site, but no plans to implement. Is there any other ways we can steer the CLI client to a faster server. It seems like there should be some low latency servers in the bay area but it seems that dallas is the closest it finds. 10ms is not much. 40ms seems a bit much
-
Worrying about few milliseconds on DNS is pointless.
You can take a look at this:
Content aside
- 1 yr agoLast active
- 2Replies
- 90Views
-
1
Following