Internet > General Internet

New DNS Service 9.9.9.9

<< < (2/2)

burakkucat:
Just for the analysts amongst us --

[Duo2 ~]$ ping -c5 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=41.2 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=40.2 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=41.6 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=40.5 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=40.7 ms

--- 8.8.8.8 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4047ms
rtt min/avg/max/mdev = 40.205/40.891/41.635/0.507 ms
[Duo2 ~]$ ping -c5 8.8.4.4
PING 8.8.4.4 (8.8.4.4) 56(84) bytes of data.
64 bytes from 8.8.4.4: icmp_seq=1 ttl=57 time=39.6 ms
64 bytes from 8.8.4.4: icmp_seq=2 ttl=57 time=39.2 ms
64 bytes from 8.8.4.4: icmp_seq=3 ttl=57 time=39.0 ms
64 bytes from 8.8.4.4: icmp_seq=4 ttl=57 time=43.0 ms
64 bytes from 8.8.4.4: icmp_seq=5 ttl=57 time=38.0 ms

--- 8.8.4.4 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4043ms
rtt min/avg/max/mdev = 38.003/39.796/43.097/1.744 ms
[Duo2 ~]$ ping -c5 9.9.9.9
PING 9.9.9.9 (9.9.9.9) 56(84) bytes of data.
64 bytes from 9.9.9.9: icmp_seq=1 ttl=58 time=40.1 ms
64 bytes from 9.9.9.9: icmp_seq=2 ttl=58 time=38.5 ms
64 bytes from 9.9.9.9: icmp_seq=3 ttl=58 time=39.4 ms
64 bytes from 9.9.9.9: icmp_seq=4 ttl=58 time=39.7 ms
64 bytes from 9.9.9.9: icmp_seq=5 ttl=58 time=39.6 ms

--- 9.9.9.9 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4046ms
rtt min/avg/max/mdev = 38.542/39.502/40.121/0.587 ms
[Duo2 ~]$

smf22:

--- Quote from: Chrysalis on November 17, 2017, 07:13:52 PM ---yeah they defenitly have geo based routing, slightly better latency for me vs google dns.

--- End quote ---

It's not mentioned in the article, but I would expect the geo based routing to be based on Anycast. The existing OpenDNS and Google Public DNS do this as described by Google in their FAQ How does Google Public DNS know where to send my queries?. Perhaps it's Anycast to get to the nearest cluster and then as they describe, the dnsdist to load balance across nodes of the cluster.

In terms of latency, I'd imagine the load on the servers is currently much lower than the other public DNS servers as there'll be fewer people using them.

art37:
Sorry to hijack an existing thread. Does anyone know the IPv4 and IPv6 secondary servers for Quad9? I have a Fritz!Box that requires both primary and secondary before it will allow a change. I recall reading somewhere that it is unwise to mix secure with insecure.

roseway:
I found this: https://www.stationx.net/improve-your-security-and-privacy-check-out-the-new-quad9-dns-service/ which recommends 149.112.112.112 as the secondary IPV4 DNS server. A whois enquiry on this number shows that it's owned by the Packet Clearing House, so it should be genuine.

dgilbert2:
Thanks for this info, will give it a try  :)

Navigation

[0] Message Index

[*] Previous page