The CNET Lounge forum

General discussion

SDRNews needs help with DNS problem. May be Cox specific.

by Owyn / February 28, 2007 9:46 PM PST

" Mark -

Thanks for writing to Todd at GNC to inquire about the show.

I changed to a different server February 1st to increase overall reliability and in the transition there have been troubles, mostly with Cox subscribers, that apparently is traceable to problems in cached DNS information and ACL lists.

You could be of great help if you could do a traceroute or tracert to 68.178.200.238, and email me a copy of the results. It appears that a machine formerly at that IP address at GoDaddy had been repeatedly attacked from various blocks within Cox but that an exact IP address for the attacker was not determined. Godaddy and Cox both have selectively blocked certain portions and addresses and if I can get listeners to do a traceroute attempt we can determine where the blockage exists. The more data points we can get will help us converge on the problem ACL.

If you have friends who are also SDR listeners or non-listeners that you could ask to send in a ping report it would really help.

Thanks,

Andy McCaskey"

http://slashdotreview.com/?p=602

A clean ping and traceroute should look something like this.

ping slashdotreview.com

Pinging slashdotreview.com [68.178.200.238] with 32 bytes of data:

Reply from 68.178.200.238: bytes=32 time=218ms TTL=49
Reply from 68.178.200.238: bytes=32 time=244ms TTL=49
Reply from 68.178.200.238: bytes=32 time=257ms TTL=49
Reply from 68.178.200.238: bytes=32 time=184ms TTL=49

Ping statistics for 68.178.200.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 184ms, Maximum = 257ms, Average = 225ms

If the ping does not resolve to 68.178.200.238, then Andy would really like to see a traceroute.


tracert 68.178.200.238

Tracing route to ip-68-178-200-238.ip.secureserver.net [68.178.200.238]
over a maximum of 30 hops:

1 73 ms 49 ms 252 ms 64.230.197.50
2 163 ms 70 ms 52 ms dis10-london14_Vlan103.net.bell.ca [64.230.222.137]
3 209 ms 170 ms 53 ms core1-london14_GE4-0.net.bell.ca [64.230.240.165]
4 122 ms 164 ms 47 ms core1-toronto63_POS9-3.net.bell.ca [64.230.242.90]
5 131 ms 102 ms 92 ms core4-toronto63_POS0-1.net.bell.ca [64.230.242.97]
6 167 ms 146 ms 59 ms core1-chicago23_pos12-0-0.net.bell.ca [64.230.147.14]
7 199 ms 56 ms 157 ms bx1-chicagodt_POS6-0.net.bell.ca [64.230.223.42]
8 76 ms 106 ms 55 ms Qwest_bx1-chicagodt_POS7_0.net.bell.ca [64.230.186.146]
9 56 ms 62 ms 398 ms cer-core-02.inet.qwest.net [205.171.139.149]
10 * * * Request timed out.
11 101 ms 101 ms 390 ms phv-edge-03.inet.qwest.net [205.171.12.110]
12 102 ms 249 ms 167 ms 63.230.242.110
13 187 ms 214 ms 106 ms ip-208-109-112-154.ip.secureserver.net [208.109.112.154]
14 124 ms 275 ms 247 ms ip-208-109-112-137.ip.secureserver.net [208.109.112.137]
15 327 ms 200 ms 115 ms ip-208-109-112-161.ip.secureserver.net [208.109.112.161]
16 134 ms 147 ms 106 ms ip-216-69-188-18.ip.secureserver.net [216.69.188.18]
17 169 ms 278 ms 178 ms ip-68-178-200-238.ip.secureserver.net [68.178.200.238]

Trace complete.

Thanks in advance for any help. If you can post any failing traceroutes here I will forward them to Andy

Discussion is locked
You are posting a reply to: SDRNews needs help with DNS problem. May be Cox specific.
The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our CNET Forums policies for details. All submitted content is subject to our Terms of Use.
Track this discussion and email me when there are updates

If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.

You are reporting the following post: SDRNews needs help with DNS problem. May be Cox specific.
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
Popular Forums
icon
Computer Newbies 10,686 discussions
icon
Computer Help 54,365 discussions
icon
Laptops 21,181 discussions
icon
Networking & Wireless 16,313 discussions
icon
Phones 17,137 discussions
icon
Security 31,287 discussions
icon
TVs & Home Theaters 22,101 discussions
icon
Windows 7 8,164 discussions
icon
Windows 10 2,657 discussions

CNET FORUMS TOP DISCUSSION

Help, my PC with Windows 10 won't shut down properly

Since upgrading to Windows 10 my computer won't shut down properly. I use the menu button shutdown and the screen goes blank, but the system does not fully shut down. The only way to get it to shut down is to hold the physical power button down till it shuts down. Any suggestions?