It doesn't seem to be a DNS problem. Your ping/tracert to
google.com
failed because the OS chose an IPv6 address, and the failure of "ping
bing.com" because the latter does not respond ping. The RTT to 8.8.8.8
(49ms) is good.
On Wed, Nov 28, 2012 at 11:24 PM, <
alai...@gmail.com> wrote:
> Hello, I have a problem similar to that. This is what I have with this
> command
>
> C:\Users\alain>nslookup -debug
www.google.com 8.8.8.8
> ------------
> Got answer:
> HEADER:
> opcode = QUERY, id = 1, rcode = NOERROR
> header flags: response, want recursion, recursion avail.
> questions = 1, answers = 1, authority records = 0, additional = 0
>
> QUESTIONS:
> 8.8.8.8.in-addr.arpa, type = PTR, class = IN
> ANSWERS:
> -> 8.8.8.8.in-addr.arpa
> name =
google-public-dns-a.google.com
> ttl = 36547 (10 hours 9 mins 7 secs)
>
> ------------
> Server:
google-public-dns-a.google.com
> Address: 8.8.8.8
>
> ------------
> Got answer:
> HEADER:
> opcode = QUERY, id = 2, rcode = NOERROR
> header flags: response, want recursion, recursion avail.
> questions = 1, answers = 6, authority records = 0, additional = 0
>
> QUESTIONS:
>
www.google.com, type = A, class = IN
> ANSWERS:
> ->
www.google.com
> internet address = 74.125.130.99
> ttl = 221 (3 mins 41 secs)
> ->
www.google.com
> internet address = 74.125.130.104
> ttl = 221 (3 mins 41 secs)
> ->
www.google.com
> internet address = 74.125.130.147
> ttl = 221 (3 mins 41 secs)
> ->
www.google.com
> internet address = 74.125.130.105
> ttl = 221 (3 mins 41 secs)
> ->
www.google.com
> internet address = 74.125.130.103
> ttl = 221 (3 mins 41 secs)
> ->
www.google.com
> internet address = 74.125.130.106
> ttl = 221 (3 mins 41 secs)
>
> ------------
> Non-authoritative answer:
> ------------
> Got answer:
> HEADER:
> opcode = QUERY, id = 3, rcode = NOERROR
> header flags: response, want recursion, recursion avail.
> questions = 1, answers = 1, authority records = 0, additional = 0
>
> QUESTIONS:
>
www.google.com, type = AAAA, class = IN
> ANSWERS:
> ->
www.google.com
> AAAA IPv6 address = 2607:f8b0:4002:c05::69
> ttl = 176 (2 mins 56 secs)
>
> ------------
> Name:
www.google.com
> Addresses: 2607:f8b0:4002:c05::69
> 74.125.130.99
> 74.125.130.104
> 74.125.130.147
> 74.125.130.105
> 74.125.130.103
> 74.125.130.106
>
> Now, if I ping
google.com this is what I have
>
> C:\Users\alain>ping
google.com
>
> Pinging
google.com [2607:f8b0:4002:c01::8a] with 32 bytes of data:
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
>
> Ping statistics for 2607:f8b0:4002:c01::8a:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>
> Next to
google.com there is no ip address like in bing example
>
> C:\Users\alain>ping
bing.com
>
> Pinging
bing.com [131.253.13.32] with 32 bytes of data:
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
>
> Ping statistics for
131.253.13.32:
> Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
>
> Now, I will ping 8.8.8.8 and 8.8.4.4
>
> C:\Users\alain>ping 8.8.8.8
>
> Pinging 8.8.8.8 with 32 bytes of data:
> Reply from
8.8.8.8: bytes=32 time=40ms TTL=45
> Reply from
8.8.8.8: bytes=32 time=58ms TTL=45
> Reply from
8.8.8.8: bytes=32 time=81ms TTL=45
> Reply from
8.8.8.8: bytes=32 time=173ms TTL=45
>
> Ping statistics for
8.8.8.8:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 40ms, Maximum = 173ms, Average = 88ms
>
> C:\Users\alain>ping 8.8.4.4
>
> Pinging 8.8.4.4 with 32 bytes of data:
> Reply from
8.8.4.4: bytes=32 time=35ms TTL=46
> Reply from
8.8.4.4: bytes=32 time=30ms TTL=46
> Reply from
8.8.4.4: bytes=32 time=32ms TTL=46
> Reply from
8.8.4.4: bytes=32 time=30ms TTL=46
>
> Ping statistics for
8.8.4.4:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 30ms, Maximum = 35ms, Average = 31ms
>
> traceroute 8.8.8.8
>
> C:\Users\alain>tracert 8.8.8.8
>
> Tracing route to
google-public-dns-a.google.com [8.8.8.8]
>
> over a maximum of 30 hops:
>
> 1 5 ms 4 ms 4 ms CISCO7186 [192.168.1.1]
> 2 13 ms 14 ms 16 ms 96.120.37.117
> 3 16 ms 13 ms 13 ms
> xe-0-2-0-0-sur01.sweetwater.fl.pompano.comcast.n
> et [68.85.125.17]
> 4 19 ms 18 ms 27 ms
> te-0-10-0-11-ar03.northdade.fl.pompano.comcast.n
> et [68.87.162.153]
> 5 17 ms 22 ms 23 ms
he-0-8-0-0-cr01.miami.fl.ibone.comcast.net
> [68.8
> 6.93.85]
> 6 35 ms 34 ms 34 ms
>
pos-0-12-0-0-cr01.56marietta.ga.ibone.comcast.ne
> t [68.86.85.5]
> 7 36 ms 34 ms 35 ms
>
pos-0-11-0-0-pe01.56marietta.ga.ibone.comcast.ne
> t [68.86.88.186]
> 8 37 ms 39 ms 61 ms 75.149.231.86
> 9 31 ms 31 ms 30 ms 72.14.239.100
> 10 31 ms 36 ms 119 ms 66.249.94.20
> 11 42 ms 41 ms 41 ms 216.239.48.41
> 12 41 ms 45 ms 41 ms 216.239.49.253
> 13 * * * Request timed out.
> 14 41 ms 41 ms 49 ms
google-public-dns-a.google.com [8.8.8.8]
>
> Trace complete.
>
> tracert
google.com
>
> C:\Users\alain>tracert
google.com
>
> Tracing route to
google.com [2607:f8b0:4002:c02::65]
>
> over a maximum of 30 hops:
>
> 1 11 ms 2 ms 1 ms fd15:d807:5e1a:0:5a6d:8fff:fe23:e70e
>
> 2 * * * Request timed out.
> 3 * * * Request timed out.
> 4 * * * Request timed out.
> 5 * * * Request timed out.
> 6 * * * Request timed out.
> 7 * * * Request timed out.
> 8 * * * Request timed out.
> 9 * * * Request timed out.
> 10 * * * Request timed out.
> 11 * * * Request timed out.
> 12 * * * Request timed out.
> 13 * * * Request timed out.
> 14 * * * Request timed out.
> 15 * * * Request timed out.
>
> 16 * * * Request timed out.
> 17 * * * Request timed out.
> 18 * * * Request timed out.
> 19 ^C
> C:\Users\alain>
>
>
> But I do can access the internet like now, but sometimes it take seconds to
> open
google.com
>
> I dont know what it is, can you help? I use comcast, I live in Miami
>
> Thank you,
> Alain