I have a friend that lives about 6 miles away from me, with TWC 30M, and he states that he has no DNS issues at all, since bringing it to his attention yesterday. I'm not looking for the misery loves company cliche, but I find more comfort in knowing that it's not isolated to something with my particular connection. =)
Here is my tracert to DNS.
C:\Users\BwoozledQ9550>tracert 209.18.47.61
Tracing route to 209.18.47.61 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 8 ms 142.254.155.109
3 444 ms 20 ms 20 ms 24.164.98.41
4 13 ms 13 ms 12 ms be22.bathoh0601r.midwest.rr.com [24.33.103.102]
5 21 ms 22 ms 15 ms be12.pltsohae01r.midwest.rr.com [65.29.1.89]
6 19 ms 22 ms 22 ms be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
7 17 ms 18 ms 17 ms agg1.clmkohpe38r.midwest.rr.com [65.29.1.247]
8 17 ms 17 ms 25 ms dns-cac-lb-01.rr.com [209.18.47.61]
Trace complete.
Here is my tracert to DNS.
C:\Users\BwoozledQ9550>tracert 209.18.47.61
Tracing route to 209.18.47.61 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 8 ms 142.254.155.109
3 444 ms 20 ms 20 ms 24.164.98.41
4 13 ms 13 ms 12 ms be22.bathoh0601r.midwest.rr.com [24.33.103.102]
5 21 ms 22 ms 15 ms be12.pltsohae01r.midwest.rr.com [65.29.1.89]
6 19 ms 22 ms 22 ms be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
7 17 ms 18 ms 17 ms agg1.clmkohpe38r.midwest.rr.com [65.29.1.247]
8 17 ms 17 ms 25 ms dns-cac-lb-01.rr.com [209.18.47.61]
Trace complete.
Uptime after last reboot 36 hours...
Startup Procedure
Procedure | Status | Comment |
Acquire Downstream Channel | Locked | |
Connectivity State | OK | Operational |
Boot State | OK | Operational |
Configuration File | OK | |
Security | Enabled | BPI+ |
DOCSIS Network Access Enabled | Allowed |
Channel | Lock Status | Modulation | Channel ID | Frequency | Power | SNR | Corrected | Uncorrectables |
1 | Locked | QAM256 | 1 | 657000000 Hz | 1.6 dBmV | 39.1 dB | 0 | 0 |
2 | Locked | QAM256 | 2 | 663000000 Hz | 1.5 dBmV | 39.1 dB | 0 | 0 |
3 | Locked | QAM256 | 3 | 669000000 Hz | 1.8 dBmV | 39.4 dB | 0 | 0 |
4 | Locked | QAM256 | 4 | 675000000 Hz | 2.5 dBmV | 38.8 dB | 0 | 0 |
5 | Locked | QAM256 | 5 | 681000000 Hz | 2.2 dBmV | 39.4 dB | 0 | 0 |
6 | Locked | QAM256 | 6 | 687000000 Hz | 2.7 dBmV | 39.4 dB | 0 | 0 |
7 | Locked | QAM256 | 7 | 693000000 Hz | 2.9 dBmV | 39.5 dB | 0 | 0 |
8 | Locked | QAM256 | 8 | 699000000 Hz | 2.4 dBmV | 39.5 dB | 0 | 0 |
9 | Locked | QAM256 | 9 | 705000000 Hz | 2.4 dBmV | 39.4 dB | 0 | 0 |
10 | Locked | QAM256 | 10 | 711000000 Hz | 3.0 dBmV | 39.6 dB | 0 | 0 |
11 | Locked | QAM256 | 11 | 717000000 Hz | 2.9 dBmV | 39.5 dB | 0 | 0 |
12 | Locked | QAM256 | 12 | 723000000 Hz | 3.4 dBmV | 39.3 dB | 0 | 0 |
13 | Locked | QAM256 | 13 | 729000000 Hz | 3.3 dBmV | 39.5 dB | 0 | 0 |
14 | Locked | QAM256 | 14 | 735000000 Hz | 2.6 dBmV | 39.4 dB | 0 | 0 |
15 | Locked | QAM256 | 15 | 741000000 Hz | 2.9 dBmV | 39.5 dB | 0 | 0 |
16 | Locked | QAM256 | 16 | 747000000 Hz | 2.8 dBmV | 39.5 dB | 0 | 0 |
Channel | Lock Status | US Channel Type | Channel ID | Symbol Rate | Frequency | Power |
1 | Locked | ATDMA | 34 | 5120 Ksym/sec | 24200000 Hz | 38.8 dBmV |
2 | Locked | TDMA | 33 | 2560 Ksym/sec | 19400000 Hz | 38.3 dBmV |
3 | Locked | ATDMA | 35 | 5120 Ksym/sec | 30600000 Hz | 39.3 dBmV |
4 | Locked | ATDMA | 36 | 2560 Ksym/sec | 37000000 Hz | 39.5 dBmV |
Current System Time: Thu Feb 09 16:41:09 2017
Microsoft Windows [Version 10.0.14393]
C:\Users\BwoozledQ9550>tracert 209.18.47.61
Tracing route to dns-cac-lb-01.rr.com [209.18.47.61]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 8 ms 8 ms 142.254.155.109
3 336 ms 88 ms 21 ms 24.164.98.41
4 13 ms 13 ms 12 ms be22.bathoh0601r.midwest.rr.com [24.33.103.102]
5 19 ms 14 ms 15 ms 65.29.1.89
6 23 ms 23 ms 22 ms be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
7 18 ms 18 ms 17 ms agg1.clmkohpe38r.midwest.rr.com [65.29.1.247]
8 17 ms 16 ms 17 ms dns-cac-lb-01.rr.com [209.18.47.61]
Trace complete.
C:\Users\BwoozledQ9550>
Here is my latest tracert, midnight.
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Users\M1-Lat6420>tracert 209.18.47.62
Tracing route to dns-cac-lb-02.rr.com [209.18.47.62]
over a maximum of 30 hops:
1 5 ms <1 ms 1 ms 192.168.0.1
2 10 ms 8 ms 9 ms 142.254.155.109
3 20 ms 34 ms 23 ms 24.164.98.41
4 14 ms 13 ms 13 ms be22.bathoh0601r.midwest.rr.com [24.33.103.102]
5 22 ms 22 ms 22 ms 65.29.1.89
6 15 ms 14 ms 22 ms be10-10.clevohek02r.midwest.rr.com [65.29.1.31]
7 17 ms 23 ms 15 ms be25.clevohek01r.midwest.rr.com [65.29.1.32]
8 17 ms 13 ms 20 ms tge9-2.clevohek03r.midwest.rr.com [65.189.140.157]
9 13 ms 12 ms 12 ms 65.29.1.153
10 13 ms 12 ms 13 ms dns-cac-lb-02.rr.com [209.18.47.62]
Trace complete.
C:\Users\M1-Lat6420>ping 209.18.47.61
Pinging 209.18.47.61 with 32 bytes of data:
Reply from 209.18.47.61: bytes=32 time=18ms TTL=57
Reply from 209.18.47.61: bytes=32 time=17ms TTL=57
Reply from 209.18.47.61: bytes=32 time=18ms TTL=57
Reply from 209.18.47.61: bytes=32 time=19ms TTL=57
Ping statistics for 209.18.47.61:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 19ms, Average = 18ms
C:\Users\M1-Lat6420>tracert www.bgr.com
Tracing route to bgr.com [192.0.79.32]
over a maximum of 30 hops:
1 1 ms <1 ms 2 ms 192.168.0.1
2 17 ms 8 ms 8 ms 142.254.155.109
3 26 ms 21 ms 32 ms 24.164.98.41
4 15 ms 13 ms 14 ms be22.bathoh0601r.midwest.rr.com [24.33.103.102]
5 27 ms 16 ms 14 ms be12.pltsohae01r.midwest.rr.com [65.29.1.89]
6 22 ms 23 ms 22 ms be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
7 33 ms 30 ms 38 ms 66.109.6.68
8 223 ms 263 ms 39 ms 66.109.6.20
9 28 ms 28 ms 30 ms 0.ae2.pr1.chi10.tbone.rr.com [107.14.17.196]
10 29 ms 29 ms 29 ms chi-b21-link.telia.net [213.248.76.97]
11 29 ms 36 ms 29 ms automattic-ic-310140-chi-b21.c.telia.net [213.248.88.162]
12 29 ms 28 ms 28 ms wordpress.com [192.0.79.32]
Trace complete.
C:\Users\M1-Lat6420>
Talked with TWC tonight, via chat. They are sending a tech next week. Support was cordial and empathized. Sent a signal to hit my model and results said connectivity was good, although I did provide that bandwidth speeds and latency was fine. All problems seemed isolated around dns issues.
As you speculated, MRaye, using Google DNS and OpenDNS at router level didn't do anything to improve matters. I have since switched back to TWC 61/62 dns servers. My neighbor, who is also a TWC internet customer, said that he is having the same kind of issues, starting back 2-3 days ago.
This where there's an issue:
3 444 ms 20 ms 20 ms 24.164.98.41
It has to be at Lakeside
Interesting path at times to Bath and then to Portage lakes to get to the DNS down in Columbus.
If there is still a head end at Lakeside, you will be on a different node than your friend. I assume you're over near Chinatown rather than towards downtown. Some buildings like Reserve sq have their own node since there's so many units in it.
Yes, I am in Chinatown. My friend in Lakewood says he has no issues on his TWC. My neighbor behind me says he has the same issues that I do.
So, how do I approach this to have it rectified?
Yes, I am in Chinatown. My friend in Lakewood says he has no issues on his TWC. My neighbor behind me says he has the same issues that I do.
So, how do I approach this to have it rectified?
*** Sorry, got duplicated. - with the issues that I am having, it takes about 4-5 tries before I can get the post to save, but one of the earlier attempts must have made it through, despite the site timing out.
I'm having issues as well...downtown cleveland. Mine's been this way since Wed night...any idea on how to fix? I changed my DNS to google but someone mentioned that wouldn't help...and they're right...
Downtown cleveland has a lot of nodes... some for a single building only.
where are you?
I recomend you both report this to TWC...
BTW, lakewoods not even close, node wise.
MsRaye,
I reported this to TWC last night and the support rep on chat was very understanding and helpful. He created a work order to have a tech visit next Friday.
What would you suggest that I have ready for him/her when the tech arrives next week? I will have printouts of my model status logs, event logs, trace routes, ping tests, etc.
What verbage should I use to direct the tech to the dns issue? Should I suggest that the node that I am on is problematic and likely overloaded?
Is there a way to switch my nodes myself (e.g. numerous router reboots, modem reboots, etc.)?
Thanks again for your advice.
HI RMSmith.
I first noticed the issue on Wednesday evening also. Actually my son brought it to my attention by asking if our internet was out.
The last time our TWC internet was out was when I went through a string of cable rips from trucks going down my street. After 3 events, TWC finally chose to route my pole drop from a higher angle and it's been great ever since...well, since Wednesday evening.