How many hops to 8.8.8.8

[90GT50]

Nah, OpenDNS reigns supreme!

Meh, using ISP DNS over here and I'm doing alright. Haven't noticed any differences with open DNS, or google's.

[Tx Redneck]

Nah, OpenDNS reigns supreme!

[Ratt]

You need to use the DNS servers that are closest to you, and preferably those that are in your ISP's network.

[Chuck_Finley]

I have a tech coming out this afternoon, but a guy just called me and said he made some billing code changes that should fix my problem. Billing codes set packet priority, my coworker explained to me.

Oh of course! I completely forgot about that one myself. But I also agree that Google's DNS is overrated. I'd suggest setting to some other ones...I personally like the old 4.2.2.2, 4.2.2.1, etc. They've been around forever and have not once given me an issue in like 15 years.

Also if you just don't seem to be getting the bandwidth you've paid for, there is a chance the node you're on is oversubscribed. Do you have a DOCSIS 3 modem, and if so, are you getting the full 8 channels down and 4 up? All subscribers in DFW should be.

Also, post a screenshot of your cable modem's signal diagnostic page.

[LS1Goat]

I don't understand why anyone would use Google Public DNS, unless you're just a sucker for poor performance.

Here's a little batch file I wrote to compare DNS response from Verizon, Open DNS, and Public DNS.

As you can see, Public DNS is a mess. Even timed out during this test.

C:\Windows NT>prompt $t

10:12:45.63nslookup www.dfwmustangs.net 68.238.96.12
Server:  nsdall01.verizon.net
Address:  68.238.96.12

Non-authoritative answer:
Name:    dfwmustangs.net
Address:  65.99.194.65
Aliases:  www.dfwmustangs.net

10:12:45.82prompt

C:\Windows NT>prompt $t

10:12:45.82nslookup www.dfwmustangs.net 208.67.222.222
Server:  resolver1.opendns.com
Address:  208.67.222.222

Non-authoritative answer:
Name:    dfwmustangs.net
Address:  65.99.194.65
Aliases:  www.dfwmustangs.net

10:12:45.87prompt

C:\Windows NT>prompt $t

10:12:45.88nslookup www.dfwmustangs.net 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
DNS request timed out.
    timeout was 2 seconds.
Name:    dfwmustangs.net
Address:  65.99.194.65
Aliases:  www.dfwmustangs.net

10:12:47.98prompt

C:\Windows NT>>pause
Press any key to continue . . .

[big_tiger]

I have a tech coming out this afternoon, but a guy just called me and said he made some billing code changes that should fix my problem. Billing codes set packet priority, my coworker explained to me.

[90GT50]

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=69ms TTL=49
Reply from 8.8.8.8: bytes=32 time=38ms TTL=49
Reply from 8.8.8.8: bytes=32 time=375ms TTL=49
Reply from 8.8.8.8: bytes=32 time=33ms TTL=49

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 375ms, Average = 128ms

Charter through VPN

[06S197GT]

Its TWC was having the same issue since Nov. had a tech come out 4 times within a 30 day period. No fix, the issue is most likely that they are tapped out on bandwidth in your neighborhood. There is no immediate fix unless they upgrade equipment. I got fed up with it and I now have U verse. I have heard of a few horror stories with Att but we'll see.

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=29ms TTL=47
Reply from 8.8.8.8: bytes=32 time=29ms TTL=47
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Reply from 8.8.8.8: bytes=32 time=29ms TTL=47
Reply from 8.8.8.8: bytes=32 time=29ms TTL=47
Reply from 8.8.8.8: bytes=32 time=29ms TTL=47
Reply from 8.8.8.8: bytes=32 time=30ms TTL=47
Reply from 8.8.8.8: bytes=32 time=30ms TTL=47
Reply from 8.8.8.8: bytes=32 time=29ms TTL=47
Reply from 8.8.8.8: bytes=32 time=31ms TTL=47
Reply from 8.8.8.8: bytes=32 time=29ms TTL=47
Reply from 8.8.8.8: bytes=32 time=30ms TTL=47
Reply from 8.8.8.8: bytes=32 time=32ms TTL=47
Reply from 8.8.8.8: bytes=32 time=29ms TTL=47
Reply from 8.8.8.8: bytes=32 time=28ms TTL=47
Reply from 8.8.8.8: bytes=32 time=29ms TTL=47
Reply from 8.8.8.8: bytes=32 time=36ms TTL=47

Ping statistics for 8.8.8.8:
Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 36ms, Average = 30ms

edit* tracert does show some packet loss, so may be something on their end after all.

[GeorgeG.]

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.69
2 37 ms 28 ms 29 ms cpe-24-27-80-1.tx.res.rr.com [24.27.80.1]
3 11 ms 12 ms 12 ms tge7-1.grpttx2801h.texas.rr.com [70.125.218.89]

4 12 ms 15 ms 15 ms tge0-8-0-9.artntxaf01r.texas.rr.com [24.175.38.1
00]
5 16 ms 15 ms 15 ms agg23.crtntxjt01r.texas.rr.com [24.175.36.224]
6 16 ms 19 ms 15 ms agg21.dllatxl301r.texas.rr.com [24.175.49.0]
7 15 ms 15 ms 16 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52]
8 14 ms 19 ms 15 ms ae1.pr1.dfw10.tbone.rr.com [107.14.17.234]
9 65 ms 66 ms 68 ms 74.125.48.65
10 20 ms 15 ms 15 ms 72.14.233.65
11 14 ms 15 ms 15 ms 72.14.237.215
12 22 ms 39 ms 23 ms 216.239.47.121
13 21 ms 21 ms 22 ms 216.239.46.59
14 * * * Request timed out.
15 22 ms 21 ms 21 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

[Tx Redneck]

And a tracert.

[Tx Redneck]

From my phone on FiOS.

[big_tiger]

My internet at home is timing out frequently, and running a trace route to 8.8.8.8 and yahoo.com it took quite a bit of hops. I tried to hassle the TWC tech support guy enough to get me to routing, but he wouldnt budge.