was meinst Du mit "der Ping nicht ansteigt" ? Die RTT, die ein 64Byte Ping braucht ?
Das ist nicht wirklich relevant, DNS records werden gecached, so dass Du nicht so oft fragen musst, wie Du eine Seite aufrufst.
Es gibt im Netz listen von oeffentlichen DNS Servern, die kannste ja alle mal anpingen, falls Dich das wirklich interessiert.. aber im Ernst, mir faellt gerade keine Applikation ein, fuer die das wirklich relevant wäre ?!
Hier mal zum Vergleich... und 4.2.2.2 ist garnicht mal so 'weit' weg. (und nebenbei leicht zu merken!!!)
bash-3.1$ ping -c 10 80.69.100.206
PING 80.69.100.206 (80.69.100.206) 56(84) bytes of data.
64 bytes from 80.69.100.206: icmp_seq=1 ttl=61 time=8.92 ms
64 bytes from 80.69.100.206: icmp_seq=2 ttl=61 time=7.85 ms
64 bytes from 80.69.100.206: icmp_seq=3 ttl=61 time=12.0 ms
64 bytes from 80.69.100.206: icmp_seq=4 ttl=61 time=10.3 ms
64 bytes from 80.69.100.206: icmp_seq=5 ttl=61 time=8.17 ms
64 bytes from 80.69.100.206: icmp_seq=6 ttl=61 time=8.01 ms
64 bytes from 80.69.100.206: icmp_seq=7 ttl=61 time=8.12 ms
64 bytes from 80.69.100.206: icmp_seq=8 ttl=61 time=8.09 ms
64 bytes from 80.69.100.206: icmp_seq=9 ttl=61 time=8.37 ms
64 bytes from 80.69.100.206: icmp_seq=10 ttl=61 time=8.17 ms
--- 80.69.100.206 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9000ms
rtt min/avg/max/mdev = 7.852/8.812/12.050/1.283 ms
bash-3.1$ ping -c 10 80.69.100.214
PING 80.69.100.214 (80.69.100.214) 56(84) bytes of data.
64 bytes from 80.69.100.214: icmp_seq=1 ttl=60 time=9.93 ms
64 bytes from 80.69.100.214: icmp_seq=2 ttl=60 time=9.42 ms
64 bytes from 80.69.100.214: icmp_seq=3 ttl=60 time=9.46 ms
64 bytes from 80.69.100.214: icmp_seq=4 ttl=60 time=10.0 ms
64 bytes from 80.69.100.214: icmp_seq=5 ttl=60 time=9.52 ms
64 bytes from 80.69.100.214: icmp_seq=6 ttl=60 time=9.66 ms
64 bytes from 80.69.100.214: icmp_seq=7 ttl=60 time=9.48 ms
64 bytes from 80.69.100.214: icmp_seq=8 ttl=60 time=9.66 ms
64 bytes from 80.69.100.214: icmp_seq=9 ttl=60 time=9.82 ms
64 bytes from 80.69.100.214: icmp_seq=10 ttl=60 time=9.65 ms
--- 80.69.100.214 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9000ms
rtt min/avg/max/mdev = 9.427/9.674/10.087/0.211 ms
bash-3.1$ ping -c 10 4.2.2.2
PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
64 bytes from 4.2.2.2: icmp_seq=1 ttl=246 time=14.2 ms
64 bytes from 4.2.2.2: icmp_seq=2 ttl=246 time=14.3 ms
64 bytes from 4.2.2.2: icmp_seq=3 ttl=246 time=14.4 ms
64 bytes from 4.2.2.2: icmp_seq=4 ttl=246 time=22.6 ms
64 bytes from 4.2.2.2: icmp_seq=5 ttl=246 time=14.2 ms
64 bytes from 4.2.2.2: icmp_seq=6 ttl=246 time=14.3 ms
64 bytes from 4.2.2.2: icmp_seq=7 ttl=246 time=14.9 ms
64 bytes from 4.2.2.2: icmp_seq=8 ttl=246 time=13.4 ms
64 bytes from 4.2.2.2: icmp_seq=9 ttl=246 time=14.5 ms
64 bytes from 4.2.2.2: icmp_seq=10 ttl=246 time=14.8 ms
--- 4.2.2.2 ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9001ms
rtt min/avg/max/mdev = 13.421/15.211/22.658/2.517 ms
bash-3.1$ traceroute 4.2.2.2
traceroute to 4.2.2.2 (4.2.2.2), 30 hops max, 38 byte packets
1 DD-WRT (192.168.1.1) 0.664 ms 0.551 ms 0.517 ms
2 10.76.128.1 (10.76.128.1) 15.830 ms 8.524 ms 7.655 ms
3 1300-MX960-01-ge-7-1-2.kerpen.unity-media.net (80.69.102.129) 8.309 ms 8.982 ms 7.995 ms
4 tge-2-2.bbr1.dus1.de.inetbone.net (213.203.213.13) 8.684 ms 9.978 ms 9.989 ms
5 tge-3-2.car2.Duesseldorf1.Level3.net (212.162.49.33) 10.083 ms 13.445 ms 15.910 ms
6 ae-33-51.ebr1.Dusseldorf1.Level3.net (4.69.139.1) 15.919 ms 8.380 ms 9.779 ms
7 ae-2-2.ebr2.Frankfurt1.Level3.net (4.69.132.138) 13.715 ms 13.103 ms 12.014 ms
8 ae-72-72.csw2.Frankfurt1.Level3.net (4.69.140.22) 20.688 ms ae-62-62.csw1.Frankfurt1.Level3.net (4.69.140.18) 14.515 ms ae-72-72.csw2.Frankfurt1.Level3.net (4.69.140.22) 14.393 ms
9 ae-21-79.car1.Frankfurt1.Level3.net (4.68.23.67) 20.411 ms ae-11-69.car1.Frankfurt1.Level3.net (4.68.23.3) 13.010 ms ae-41-99.car1.Frankfurt1.Level3.net (4.68.23.195) 14.089 ms
10 vnsc-bak.sys.gtei.net (4.2.2.2) 14.400 ms 12.981 ms