Examples (win ones German though):
In my case it's getting the DNS info from my router ;-)
-c 4 is to restrict it to 4 times otherwise you'll have to abort it with Ctrl-C after a while
Note that the trace on linux had some trouble with finding the last hop(s) maybe because the route changed in the middle of it. Note as well that traceroute is not available by default on all linux systems - you might have to install the package.
"Win check DNS"
C:\Users\janlue>nslookup shard.ryzom.com
Server: router.luetke.lan
Address: 2001:4dd0:ff00:8b12:6::1
Nicht autorisierende Antwort:
Name: shard.ryzom.com
Address: 178.33.44.35
"Linux check DNS"
luetke@media ~ $ dig su1.ryzom.com
; <<>> DiG 9.8.1-P1 <<>> su1.ryzom.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 391
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;su1.ryzom.com. IN A
;; ANSWER SECTION:
su1.ryzom.com. 28654 IN A 178.33.44.35
;; Query time: 2 msec
;; SERVER: 192.168.6.1#53(192.168.6.1)
;; WHEN: Wed Oct 16 14:16:17 2013
;; MSG SIZE rcvd: 47
In my case it's getting the DNS info from my router ;-)
"Win Ping"
C:\Users\janlue>ping shard.ryzom.com
Ping wird ausgeführt für shard.ryzom.com [178.33.44.35] mit 32 Bytes Daten:
Antwort von 178.33.44.35: Bytes=32 Zeit=28ms TTL=56
Antwort von 178.33.44.35: Bytes=32 Zeit=27ms TTL=56
Antwort von 178.33.44.35: Bytes=32 Zeit=27ms TTL=56
Antwort von 178.33.44.35: Bytes=32 Zeit=27ms TTL=56
Ping-Statistik für 178.33.44.35:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 27ms, Maximum = 28ms, Mittelwert = 27ms
"Linux Ping"
luetke@media ~ $ ping -c 4 su1.ryzom.com
PING su1.ryzom.com (178.33.44.35) 56(84) bytes of data.
64 bytes from 178.33.44.35: icmp_req=1 ttl=56 time=27.2 ms
64 bytes from 178.33.44.35: icmp_req=2 ttl=56 time=27.9 ms
64 bytes from 178.33.44.35: icmp_req=3 ttl=56 time=27.2 ms
64 bytes from 178.33.44.35: icmp_req=4 ttl=56 time=28.0 ms
--- su1.ryzom.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 15157ms
rtt min/avg/max/mdev = 27.215/27.613/28.070/0.436 ms
-c 4 is to restrict it to 4 times otherwise you'll have to abort it with Ctrl-C after a while
"Win trace"
C:\Users\janlue>tracert shard.ryzom.com
Routenverfolgung zu shard.ryzom.com [178.33.44.35] über maximal 30 Abschnitte:
1 <1 ms <1 ms 4 ms router.luetke.lan [192.168.6.1]
2 11 ms 9 ms 8 ms 62.214.64.52
3 24 ms 10 ms 10 ms 62.214.110.57
4 179 ms 198 ms 204 ms 62.214.106.90
5 19 ms 20 ms 19 ms 62.214.106.65
6 * 20 ms * decix.routers.ovh.net [80.81.192.209]
7 29 ms 28 ms 60 ms rbx-g2-a9.fr.eu [91.121.131.201]
8 29 ms * 27 ms vss-6a-6k.fr.eu [91.121.128.40]
9 27 ms 27 ms 27 ms 178.33.44.35
Ablaufverfolgung beendet.
"Linux trace"
traceroute su1.ryzom.com
traceroute to su1.ryzom.com (178.33.44.35), 30 hops max, 60 byte packets
1 router.luetke.lan (192.168.6.1) 0.733 ms 1.142 ms 1.562 ms
2 62.214.64.52 (62.214.64.52) 11.456 ms 13.551 ms 15.054 ms
3 62.214.110.57 (62.214.110.57) 152.616 ms 152.954 ms 153.113 ms
4 62.214.106.90 (62.214.106.90) 27.540 ms 30.607 ms 62.214.106.94 (62.214.106.94) 31.393 ms
5 62.214.106.69 (62.214.106.69) 41.017 ms 41.354 ms 42.822 ms
6 decix.routers.ovh.net (80.81.192.209) 45.429 ms * *
7 rbx-g2-a9.fr.eu (91.121.131.201) 50.528 ms 28.825 ms 58.231 ms
8 vss-6a-6k.fr.eu (91.121.128.40) 58.618 ms * *
9 * * *
...
30 * * *
Note that the trace on linux had some trouble with finding the last hop(s) maybe because the route changed in the middle of it. Note as well that traceroute is not available by default on all linux systems - you might have to install the package.
---