NextDNS connects to different locations
Hello everyone! NextDNS connects to different locations (countries). Could you tell me if this is normal? Sometimes it’s Ukraine, sometimes Sweden, sometimes somewhere else entirely… As far as I understand, the IP addresses 45.90.28.* and 45.90.30.* are anycast1 and anycast2 respectively. For DoT and DoH, it connects using some other algorithm (currently ultralow1; sometimes it’s anycast, and sometimes it’s neither anycast nor ultralow). Is there any way to fix this so that it always connects to zepto-mow (without being tied to a specific server like https://zepto-mow-1.edge.nextdns.io)?
https://nextdns.io/diag/a22a68e0-cd42-11f1-92f4-51a194747dc3
I’ve also noticed that some of your features have been in beta for several years now, and new security features have recently appeared that are actually in early access (essentially alpha status, an even earlier/more unpolished stage). Could you tell me how many more years these features will remain in beta, and how many decades the new security features will remain in alpha?)) It just feels as though the developers have simply forgotten the password))
2 replies
-
Diagnostics from version 2.0.1
https://nextdns.io/diag/a261c160-cd96-11f1-8e7c-235add6fcb0a
-
Via DoH, it chose zepto-mow instead, although this is not consistent — https://nextdns.io/diag/e0a17d90-cd9f-11f1-9552-6b687ed67cad
Via WARP colo=DME, it should select zepto-mow rather than zepto-iev — https://nextdns.io/diag/d0a9dad0-cda0-11f1-89d9-b9f7cf744e88
When using WARP colo=FRA (loc=RU), it should select the server in Frankfurt (zepto-fra??), not zepto-iev (or mow) — https://nextdns.io/diag/8441a780-cda1-11f1-9552-6b687ed67cad
I’ve also noticed that you don’t list the UK as a country for log storage, but it’s still on the homepage)
“Meet your data residency requirements by choosing where your logs are stored — United States, European Union, United Kingdom or Switzerland.”
Content aside
- 19 hrs agoLast active
- 2Replies
- 12Views
-
1
Following
