anexia-par (IPv6) from Free
Hello,
From today anexia-par (IPv6) has a bad latency from Free only with ipv6.
It’s strange because i use nextdns cli on two server at home and the master connect to anexia-par (IPv6) and the secondary to netbarista-par (ipv6) on the same network.
regards
4 replies
-
Please provide a https://nextdns.io/cli
-
Do you mean my nextdns cli configuration / log or a https://nextdns.io/diag ?
Right now my two nextdns cli are switching between ipv4 / ipv6 with anexia-par / netbarista-par / virtua-par.
Maybe Free is working on routing network. Maybe because Free is now on France-IX ?
I will try later and let you know. Thank's ;)
-
After some test, the issue is now resolved.
1) Two NextDns Cli on the same network is not efficient in case of a device answering more slowly than the other. Also, you need to be sure that the two cli never try to get a DNS answer from the other. It's more about the OS configuration than the CLI itself.
2) The route used by NextDns Cli was wrong even after a stop / start / reboot of the server. I have to purge NextDns Cli and proceed with a clean installation. (Caching somewhere ?).
3) The Freebox was slow to provide ipv6 over the LAN network and some devices having trouble to get the IPV6 address. That's strange because with the DNS of NextDns in the DHCP section of the Freebox, I don't have this problem (I tried several times).
The Best option is running just one NextDns Cli with a device having a low latency (cpu / IO wait) even if the CLI is not CPU intensive. Also, it's best to have the NextDns Cli working before the others devices on the LAN get's the DHCP request to be sure that ipv4 / ipv6 resolution is working.
3 ms with netbarista-par / anexia-par / virtua-par is excellent !
Content aside
- 1 yr agoLast active
- 4Replies
- 103Views
-
2
Following