2a07:a8c0:: unreachable
Hi,
Since January 29, ipv6 DNS server 2a07:a8c0:: and 2a07:a8c1:: are not reachable from my location. Setting primary and secondary ipv6 DNS to 2a07:a8c0:: and 2a07:a8c1:: has failed since January 29, 2025. I've had to set my DNS to 8.8.8.8.
Diag:
Testing IPv6 connectivity
available: false
Fetching https://test.nextdns.io
status: unconfigured
client: x
resolver: 74.125.42.154
Fetching PoP name for ultra low latency primary IPv4 (ipv4.dns1.nextdns.io)
vultr-atl: 10.042ms
Fetching PoP name for ultra low latency secondary IPv4 (ipv4.dns2.nextdns.io)
anexia-atl: 10.094ms
Fetching PoP name for anycast primary IPv4 (45.90.28.0)
zepto-xrs: 20.252ms
Fetching PoP name for anycast secondary IPv4 (45.90.30.0)
anexia-atl: 8.151ms
Pinging PoPs
anexia-atl: 10.163ms
vultr-atl: 10.153ms
tier-clt: 14.209ms
zepto-iad: 20.365ms
hydron-clt: 20.444ms
anexia-mnz: 24.291ms
teraswitch-pit: 24.238ms
cloudzy-pit: 26.229ms
vultr-chi: 30.407ms
anexia-chi: 31.465ms
Thanks.
1 reply
-
Good luck with that, I'm waiting for a reply since 27/jan. It seams that everybody left the ship. https://help.nextdns.io/t/y4yl5tb
That being said, you can try to force the usage of other servers instead of the anycast ones.
Take a look at
https://help.nextdns.io/t/h7hkyw2 or
https://help.nextdns.io/t/p8h0g23?r=83h0w4t
on how-to force a especific server, from those listed on ping ou diag.You can prepend those names with ipv4- or ipv6- to force the usage of IPv4 or IPv6, respectivily, as stated in https://help.nextdns.io/t/60htdz3 (but don't follow that solution, just take a look on the naming conventions).
Kind regards,
Rodrigo
Content aside
- 1 mth agoLast active
- 1Replies
- 35Views
-
2
Following