traceroute fails for IPv4 but works for IPv6

309 views
Skip to first unread message

timk...@gmail.com

unread,
May 19, 2012, 7:45:19 PM5/19/12
to public-dn...@googlegroups.com
5/19/12 traceroute fails for IPv4 but works for IPv6.  Browser seems to work ok on all sites.  Linux Fedora 16  (Windows 7 traceroute (tracert) works for both IPv4 & IPv6)


[tim@localhost ~]$ traceroute -n -w 2 -q 2 -m 30 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
 1  192.168.1.254  2.077 ms  2.913 ms
 2  151.164.186.20  23.583 ms  24.594 ms
 3  64.161.163.214  18.174 ms  20.340 ms
 4  * *
 5  12.83.60.130  29.863 ms *
 6  * *
 7  * *
 8  * *
 9  * *
10  * *
11  * *
12  * *
13  * *
14  * *
15  * *
16  * *
17  * *
18  * *
19  * *
20  * *
21  * *
22  * *
23  * *
24  * *
25  * *
26  * *
27  * *
28  * *
29  * *
30  * *
[tim@localhost ~]$ dig @8.8.8.8 www.google.com.

; <<>> DiG 9.8.2-RedHat-9.8.2-1.fc16 <<>> @8.8.8.8 www.google.com.
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62174
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;; ANSWER SECTION:
www.l.google.com. 299 IN A 74.125.224.177
www.l.google.com. 299 IN A 74.125.224.178
www.l.google.com. 299 IN A 74.125.224.176
www.l.google.com. 299 IN A 74.125.224.179
www.l.google.com. 299 IN A 74.125.224.180

;; Query time: 53 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat May 19 16:21:32 2012
;; MSG SIZE  rcvd: 132


[tim@localhost ~]$ traceroute -n -w 2 -q 2 -m 30 2001:4860:4860::8888
traceroute to 2001:4860:4860::8888 (2001:4860:4860::8888), 30 hops max, 80 byte packets
 1  2602:304:cf9b:e3e9::  1.205 ms  2.102 ms
 2  2602:300:c533:1510::8  14.037 ms  16.614 ms
 3  2001:1890:ff:ffff:12:122:127:48  21.229 ms  23.036 ms
 4  2001:1890:c00:4b00::115e:e307  25.648 ms  28.216 ms
 5  2001:4860::1:0:29b3  58.419 ms 2001:4860::1:0:991  33.200 ms
 6  2001:4860::8:0:2995  35.472 ms 2001:4860::8:0:2996  38.082 ms
 7  2001:4860::8:0:2f03  101.606 ms 2001:4860::8:0:2f04  104.132 ms
 8  2001:4860::2:0:a7  126.225 ms  159.351 ms
 9  2001:4860:0:1::109  111.341 ms  126.847 ms
10  2001:4860:4860::8888  106.655 ms  103.352 ms
[tim@localhost ~]$ dig @2001:4860:4860::8888 www.google.com. AAAA

; <<>> DiG 9.8.2-RedHat-9.8.2-1.fc16 <<>> @2001:4860:4860::8888 www.google.com. AAAA
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17009
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;www.google.com. IN AAAA

;; ANSWER SECTION:

;; AUTHORITY SECTION:
l.google.com. 600 IN SOA ns2.google.com. dns-admin.google.com. 1486077 900 900 1800 60

;; Query time: 149 msec
;; SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888)
;; WHEN: Sat May 19 16:22:33 2012
;; MSG SIZE  rcvd: 102

[tim@localhost ~]$ 

Yunhong Gu

unread,
May 19, 2012, 10:43:17 PM5/19/12
to public-dn...@googlegroups.com
sometimes switches may block traceroute. Since you can still get DNS answer from 8.8.8.8, the network should be fine.


--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to
public-dns-disc...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================

timk...@gmail.com

unread,
May 22, 2012, 1:23:34 AM5/22/12
to public-dn...@googlegroups.com
Thanks for the reply. Guess everything is ok, great.
Reply all
Reply to author
Forward
0 new messages