Possible internal Surpass DNS corruption. - Page 2

The Wicked Flea · May 20th, 2007, 10:10 PM

Well, I couldn't get to Surmunity or SurpassHosting for the last 1.5 hours, and here's the tracert. This is a mess, I can't tell if it is my ISP, someone inbetween, or what. Is this normal growing pains?

Code:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\[..]>tracert surmunity.com

Tracing route to surmunity.com [72.29.64.189]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  [..]
  2     *        *        *     Request timed out.
  3    10 ms    10 ms    12 ms  10.23.1.1
  4    12 ms    11 ms    11 ms  at-2-0-0-1710.CORE-RTR1.HAG.verizon-gni.net [130
.81.12.13]
  5    19 ms    24 ms    24 ms  so-3-3-1-0.BB-RTR1.RES.verizon-gni.net [130.81.2
0.20]
  6    20 ms    15 ms    15 ms  so-6-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81
.10.90]
  7    18 ms    20 ms    16 ms  eqix.asbn.twtelecom.net [206.223.115.36]
  8    18 ms    17 ms    18 ms  66.192.240.17
  9    64 ms    64 ms    65 ms  dist-02-so-0-0-0-0.mtld.twtelecom.net [66.192.24
3.15]
 10    83 ms    68 ms    82 ms  66.192.243.194
 11    69 ms    82 ms    70 ms  66.162.30.58
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14  ^C
C:\Documents and Settings\[..]>

And of course, that period had to occur right when I was going to sign in to submit a ticket.

The Wicked Flea · May 21st, 2007, 12:26 PM

Okay, I changed my DNS information to another ISP I have used out in Montana. Verizon is just too big to care about how their infrastructure works, but I know this company does. But, I cannot tracert or hit the site through their DNS information either, and in fact it dies in the exact same IP address.

Is HostDime your parent company? Why do I keep entering at this same static IP Address that doesn't work, yet just about everyone else goes through a different IP and hits the site? I did a tracert through DNSSTUFF.COM and it hit the site fine. The dns information I changed to was this.

Code:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\[..]>tracert sh105.surpasshosting.com

Tracing route to sh105.surpasshosting.com [72.29.93.156]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  [..]
  2     *        *        *     Request timed out.
  3     9 ms     9 ms     9 ms  10.23.1.1
  4    10 ms     9 ms    10 ms  at-2-0-0-1711.CORE-RTR2.HAG.verizon-gni.net [130
.81.12.17]
  5    10 ms    10 ms    10 ms  so-0-0-0-0.CORE-RTR1.HAG.verizon-gni.net [130.81
.18.152]
  6    14 ms    15 ms    15 ms  so-3-3-1-0.BB-RTR1.RES.verizon-gni.net [130.81.2
0.20]
  7    15 ms    15 ms    15 ms  0.so-7-0-0.XL1.IAD8.ALTER.NET [152.63.36.201]
  8    15 ms    15 ms    15 ms  0.so-6-0-0.BR1.IAD8.ALTER.NET [152.63.32.157]
  9    15 ms    15 ms    16 ms  OC-48-1-1-0-edge1.Washington1.Level3.net [4.68.1
27.25]
 10    16 ms    21 ms    18 ms  ae-31-51.ebr1.Washington1.Level3.net [4.68.121.3
0]
 11    18 ms    15 ms    48 ms  ae-2.ebr1.Atlanta2.Level3.net [4.69.132.85]
 12    45 ms    53 ms    54 ms  ae-6-6.car1.Orlando1.Level3.net [4.69.133.77]
 13    53 ms    60 ms    53 ms  ae-6-6.car1.Orlando1.Level3.net [4.69.133.77]
 14    60 ms    60 ms    60 ms  DimeNoc-edge1.HostDime.com [4.79.116.26]
 15     *        *       60 ms  72-29-88-34.static.dimenoc.com [72.29.88.34]
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *     ^C
C:\Documents and Settings\[..]>

DNSStuff's Tracert:

Code:

1	0	*	*	0.8 ms	
 	 
	74.53.59.130 AS0
IANA-RSVD-0	 82.3b.354a.static.theplanet.com.	 	255	US	Unix: 15:08:31. 46
2	16	*	*	0.9 ms [+0ms]	
 	 
	12.96.160.42 AS21844
THEPLANET-AS	 vl2.dsr02.dllstx2.theplanet.com.	 0 miles [+0] 	254	US	Unix: 15:08:31.264
3	93	*	*	0.9 ms [+0ms]	
 	 
	70.87.253.121 AS21844
THEPLANET-AS	 79.fd.5746.static.theplanet.com.	 0 miles [+0] 	253	US	Unix: 15:08:31.563
4	0	*	*	0.9 ms [+0ms]	
 	 
	70.87.253.25 AS21844
THEPLANET-AS	 et3-2.ibr04.dllstx3.theplanet.com.	 -1 miles [+0] 0 miles [+0] 	61	US	[Router did not respond]
5	1	*	*	1.6 ms [+0ms]	
 	 
	4.71.122.1 AS3356
Level3	 te-3-1.car4.dallas1.level3.net.	 -1 miles [+0] 0 miles [+0] 	251	US	Unix: 15:08:31.376
6	3	*	*	3.0 ms [+1ms]	
 	 
	4.68.122.94 AS3356
Level3	 ae-31-53.ebr1.dallas1.level3.net.	 -1 miles [+0] 0 miles [+0] 	250	US	Unix: 15:08:31.429
7	45	*	*	45 ms [+42ms]	
 	 
	4.69.133.69 AS3356
Level3	 ae-9-9.car2.orlando1.level3.net.	 -1 miles [+0] 0 miles [+0] 	249	US	Unix: 15:08:31.514
8	46	*	*	46 ms [+0ms]	
 	 
	4.79.118.38 AS3356
Level3	 hostdime.car2.orlando1.level3.net.	 -1 miles [+0] 0 miles [+0] 	246	US	Unix: 15:08:31.561
9	62	*	*	62 ms [+16ms]	
 	 
	72.29.93.156 AS33182
DIMENOC---HOSTDIME	 
[Reached Destination]sh105.surpasshosting.com.	 -1 miles [+0] 	54	US	[Router did not respond]

I'll submit a ticket as soon as I can, but this clearly is a broadcast problem with SH105. That makes for 2 ISPs that have trouble accessing the site. And it can't be my PC because this happens to every computer in our house. (EDIT: And just so you know refreshing the DNS cache did nothing, the data I get is still corrupted.)

**Daniel** · May 21st, 2007, 1:06 PM

Hiya,

From what I saw in your traceroutes, this is definitely not an issue on your side, as you are hitting the datacenter, thus you are not getting filtered by our routers, or experiencing some weird routing issue with your ISP. So that's out of the way.

15 * * 60 ms 72-29-88-34.static.dimenoc.com [72.29.88.34]

That's our core to core peering IP, meaning you're hitting our second router, which is a good thing, as the next hop is supposed to be the server. About the only possibility here would be that you got somehow accidentally blocked by the servers' firewall.

I am going to be doing some quick cleaning up on the server in a minute, as there are literally thousands of DROP rules in the servers' firewall, which I am sure that some of them are not legitimate. False positives do occur from time to time, and I can almost guarantee this is the case.

Let me know if you are experiencing any problems within the next 15-20 minutes.

Regards,

The Wicked Flea · May 21st, 2007, 1:12 PM

Thank you! After some tests of our own we just hit the site with our last attempt.

That did work.

**Daniel** · May 21st, 2007, 1:56 PM

I'm glad to hear it

Let us know if anything else comes up.

gbigg · May 21st, 2007, 5:37 PM

Hi there i seem to be having the same problem:

Code:

Tracing route to gbigg.co.uk [66.7.199.38]

over a maximum of 30 hops:



  1    <1 ms    <1 ms    <1 ms  192.168.0.1 
  2     *       15 ms    15 ms  adsl-bba3.th.eclipse.net.uk [82.153.1.4] 
  3    14 ms    15 ms    14 ms  82.153.2.49 
  4    14 ms    14 ms    14 ms  ge-1-1.metro2-londencyh00.London1.Level3.net [212.187.151.157] 
  5    15 ms    15 ms    13 ms  so-1-3-0.gar1.London1.Level3.net [212.113.3.25] 
  6    20 ms    17 ms    17 ms  ae-19-55.ebr1.London1.Level3.net [4.68.116.158] 
  7    18 ms    17 ms    17 ms  ae-1-100.ebr2.London1.Level3.net [4.69.132.118] 
  8    92 ms    91 ms    90 ms  ae-4.ebr1.NewYork1.Level3.net [4.69.132.109] 
  9    91 ms   103 ms   179 ms  ae-3.ebr1.Washington1.Level3.net [4.69.132.89] 
 10   115 ms     *      107 ms  ae-2.ebr1.Atlanta2.Level3.net [4.69.132.85] 
 11   160 ms   134 ms   159 ms  ae-6-6.car1.Orlando1.Level3.net [4.69.133.77] 
 12   138 ms   112 ms   113 ms  DimeNoc-edge1.HostDime.com [4.79.116.26] 
 13   192 ms   165 ms   152 ms  72-29-88-34.static.dimenoc.com [72.29.88.34] 
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *

If I go through a proxy, i can reach the site with no troubles at all, it seems a firewall is blocking me.

Is there a remedy that i can do to solve this?

May 21st, 2007, 1:12 PM	#13 (permalink)
The Wicked Flea Registered User Seasoned Poster Joined in Jul 2006 Lives in USA Hosted on SH133 57 posts Gave thanks: 11 Thanked 1 Time in 1 Post	Thank you! After some tests of our own we just hit the site with our last attempt. That did work. __________________ SH133:

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search

May 21st, 2007, 1:06 PM	#12 (permalink)
Daniel Sysadmin Seasoned Poster Joined in Feb 2005 81 posts Gave thanks: 0 Thanked 54 times	Hiya, From what I saw in your traceroutes, this is definitely not an issue on your side, as you are hitting the datacenter, thus you are not getting filtered by our routers, or experiencing some weird routing issue with your ISP. So that's out of the way. 15 * * 60 ms 72-29-88-34.static.dimenoc.com [72.29.88.34] That's our core to core peering IP, meaning you're hitting our second router, which is a good thing, as the next hop is supposed to be the server. About the only possibility here would be that you got somehow accidentally blocked by the servers' firewall. I am going to be doing some quick cleaning up on the server in a minute, as there are literally thousands of DROP rules in the servers' firewall, which I am sure that some of them are not legitimate. False positives do occur from time to time, and I can almost guarantee this is the case. Let me know if you are experiencing any problems within the next 15-20 minutes. Regards,

May 21st, 2007, 1:56 PM	#14 (permalink)
Daniel Sysadmin Seasoned Poster Joined in Feb 2005 81 posts Gave thanks: 0 Thanked 54 times	I'm glad to hear it Let us know if anything else comes up.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)