dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
23

bulletsam
join:2008-04-08
Charleston, IL

bulletsam to sway0004

Member

to sway0004

Re: [IL] mediacomcable.com

Tracing route to www.mediacomcable.com [74.84.103.140]
over a maximum of 30 hops:

1 7 ms 8 ms 7 ms 10.128.60.1
2 62 ms 65 ms 63 ms 172.30.9.185
3 36 ms 35 ms 38 ms 172.30.9.161
4 37 ms 36 ms 38 ms 12.91.232.13
5 57 ms 55 ms 56 ms cr2.sl9mo.ip.att.net [12.122.152.202]
6 44 ms 43 ms 45 ms cr2.kc9mo.ip.att.net [12.122.28.89]
7 58 ms 57 ms 72 ms 12.122.150.205
8 82 ms 80 ms 84 ms 12.250.192.102
9 * * * Request timed out.
10 89 ms 84 ms 90 ms www.mediacomcable.com [74.84.103.140]

Trace complete.

I can get there... slow, but I can.
GLIMMER
join:2004-01-17
Fisher, IL

GLIMMER

Member


Tracing route to www.mediacomcable.com [74.84.103.140]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 8 ms 10.132.4.1
3 * 10.132.4.1 reports: Destination net unreachable.

Trace complete.

tracert www.google.com

Tracing route to www.google.com [173.194.46.20]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 8 ms 10.132.4.1
3 8 ms 9 ms 10 ms 172.30.89.129
4 10 ms 10 ms 9 ms 172.30.35.65
5 21 ms 19 ms 19 ms 12.94.137.53
6 32 ms 31 ms 31 ms cr2.kc9mo.ip.att.net [12.122.150.138]
7 38 ms 31 ms 36 ms cr1.dlstx.ip.att.net [12.122.28.85]
8 29 ms 28 ms 28 ms gar22.dlstx.ip.att.net [12.122.85.65]
9 29 ms 31 ms 31 ms 12.249.185.238
10 29 ms 29 ms 29 ms 72.14.233.67
11 29 ms 30 ms 29 ms 209.85.240.79
12 30 ms 29 ms 29 ms dfw06s27-in-f20.1e100.net [173.194.46.20]

Trace complete.
sway0004
join:2005-04-29
Surprise, AZ

sway0004

Member

okay i wanted to tell my thoughts on the whole remove my router idea.. its flawed as it works now after 12 hours down.. it was a dns issue with mediacom.. plain and simple..

my router hasnt been powered down or reconfigured

the tracert i gave was recieving the 2nd hop at the 10. on mediacoms end..

glimmer helped create the same issue (thanks) if you ask him he will say it works now too i bet..

i know websites very well apache freaks out alot..

MediacomChad
Mediacom Social Media Relations Team
Premium Member
join:2010-01-20
Gulf Breeze, FL

MediacomChad

Premium Member

I am glad it is working now. Let me know if you have any other issues going forward and I will be happy to look into it.

dgschoel
Premium Member
join:2001-09-07
Ames, IA

dgschoel

Premium Member

Not working for me today on mediacom network in my home and also my phone browser using 3G network.

MediacomChad
Mediacom Social Media Relations Team
Premium Member
join:2010-01-20
Gulf Breeze, FL

MediacomChad

Premium Member

We are currently working with our Tier-2 and NOC to get this issue resolved.

iSpud
@qwest.net

iSpud

Anon

You could use a public DNS like google's DNS servers instead of the default mediacom ones, and they'd probably be more reliable.

Google: 8.8.8.8, 8.8.4.4
rfc1918
join:2013-02-01
Des Moines, IA

rfc1918 to sway0004

Member

to sway0004
quote:
it was a dns issue with mediacom.. plain and simple..
I'm curious how this looks like a DNS issue to you.

C:\Users\iconz>tracert www.mediacomcable.com

Tracing route to www.mediacomcable.com [74.84.103.140]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 192.168.1.1
2 10 ms 12 ms 18 ms 10.132.42.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * 10.132.42.1 reports: Destination net unreachable.


See that in bold up there? In that whole traceroute, all DNS does is convert www.mediacomcable.com to 74.84.103.140, which was successful, otherwise you'd have gotten 'www.mediacomcable.com... unknown host'. The fact that you couldn't get there had nothing to do with the DNS. It was a network issue.