Connecting to fastest server
I'm running NextDNS on pfsense via CLI, but for some reason, it never wants to connect to the fastest servers however many times I try.
I've tried rebooting pfsense and restarting the service, but it always connects to annexia-man when others are consistently faster.
https://nextdns.io/diag/fb76b700-7d5b-11ec-a639-ab002b683e5c
Is there a way to force / steer it to connect to others? Or what is the logic that's used to connect to the server it connects to?
13 replies
-
Chris, I have same issue on pfSense as well ("server": "anexia-chi-1"). Very briefly I saw OVH (closer to me in Canada then Australian servers).
Yes, I'd like to find a way to choose closer servers as well. I tried restarting as you and restarted the resolver but to no avail. Same server.
-
My situation isn't as bad as you guys, but it would still be great to be able to connect to the closest / fastest servers.
It would be good to be able to 'force' or at least have the ability to select server priorities or similar.
Is anyone from NextDNS available to comment?
-
I noticed this too on my pfsense box (not sure it's related to pfsense).
The (really dirty / hacky) way i got round it was create a floating rule to block traffic to the IPs of the anexia-man server, which now sends me over to zept-lon which is consistently lower on latency as well as a few less hops.
The issue you might run into is private DNS on android wont work, however i got round this by only blocking traffic from the pfsense box (where i run the cli proxy) which allows other devices to contact whatever server they want (which tend to be london anyway!)
-
I have the same problem from Turkey. Connecting to Viana instead of connecting to Istanbul server. The latency between the two servers is huge.
Content aside
- 2 yrs agoLast active
- 13Replies
- 962Views
-
5
Following