Synchro issue between NextDNS server
Hi,
there is currently an issue related to synch issue between nextdns servers.
There is an issue between (for example)
45.90.28.0 and 45.90.30.0
Same issue between ipv6 servers.
to reproduce, just make a change in your profile (deny host/domain for example), and try to resolve on both servers. You will see different answers. From my location at least (France).
Thanks
29 replies
-
For example I am trying to block/unblock domain gameloft.com. On the related profile, this domain is currently unblock (but it was blocked before) :
# nslookup gameloft.com 45.90.30.229
Server:45.90.30.229
Address:45.90.30.229#53Non-authoritative answer:
Name:gameloft.com
Address: 0.0.0.0
Name:gameloft.com
Address: ::# nslookup gameloft.com 45.90.28.229
Server:45.90.28.229
Address:45.90.28.229#53Non-authoritative answer:
Name:gameloft.com
Address: 208.71.186.80the second lookup (45.90.28.229) is correct, but the first is not. Even if I wait some times or try again to block / unblock , no change.
-
It seems that there is currently a routing issue :
# curl https://dns.nextdns.io/info --connect-to ::45.90.28.0 {"locationName": " Paris, France", "pop": "netbarista-par", "rtt": 13103} # curl https://dns.nextdns.io/info --connect-to ::45.90.30.0 {"locationName": " Frankfurt, Germany", "pop": "vultr-fra", "rtt": 18160}
Previously, it was :
$ curl https://dns.nextdns.io/info --connect-to ::45.90.28.0 {"locationName": " Paris, France", "pop": "netbarista-par", "rtt": 11829} $ curl https://dns.nextdns.io/info --connect-to ::45.90.30.0 {"locationName": " Paris, France", "pop": "virtua-par", "rtt": 12750}
Why Frankfurt for 45.90.30.0 instead of Paris ?
It appears today at about 12h30 (Paris GMT+1).
thanks
Content aside
-
1
Likes
- 11 mths agoLast active
- 29Replies
- 285Views
-
4
Following