Skip to content
MandarinCreative's profile

New Contributor

 • 

7 Messages

Monday, August 24th, 2015 10:00 AM

Some Incoming HTTP traffic gets stopped at Comcast Node and never makes it to our site

We have been getting sporadic complaints from some users of our website (which is hosted on our Business Class connection), that they cannot "get to" our website.. .www.centerlinescores.com.

 

After multiple levels of debugging and troubleshooting to make sure that these users (about 10 total out of 40K monthly) were not doing something silly, we've identified one commonality.  For all those users who cannot get to the site, we have asked them to run a traceroute.  

 

IN EVERY. SINGLE. CASE.  that has replied to us with results.  Their traceroute request gets stopped dead in its tracks at  c-76-18-194-16.hsd1.fl.comcast.net (76.18.194.16).  Immediately before this final entry, we see these traceroutes hop to te-6-1-acr02.mandarin.fl.jacksvil.comcast.net successfully and then are stopped at the 76.18.194.16.

 

As I mentioned, this is ONLY for a very small handful of users.

 

Is there anything I can do to debug this further or anything I can do in DNS to avoid this node?  Any help at all will be tremendously appreciated.

 

Jay L Stevens

 

Advocate

 • 

1.4K Messages

9 years ago

Hello MandarinCreative and welcome,

 

Well, I too am getting an HTTP 440 error when trying to access your website for unknown reasons. Your zone file following information shows that this is not under the Comcast umbrella :

 

A 50.253.68.225
 
MX 30 ALT2.ASPMX.L.GOOGLE.com.
40 ASPMX2.GOOGLEMAIL.com.
50 ASPMX3.GOOGLEMAIL.com.
20 ALT1.ASPMX.L.GOOGLE.com.
10 ASPMX.L.GOOGLE.com.
 
CNAME No CNAME record found.
 
NS ns48.domaincontrol.com.
ns47.domaincontrol.com.
 
PTR No PTR record found.
 
SOA ns47.domaincontrol.com. dns.jomax.net
2015080500 28800 7200 604800 600

 

So, the above record information show this is a GOOGLE hosted website and you must contact them for proper records correction. All companies internetwork routers/brouters may have some such errors but you need to have much more consistent error conditions than 10 of 40000 for this to be a valid issue.

 

Hope this helps you out.

New Contributor

 • 

7 Messages

9 years ago

It doesn't help actually.

 

This is NOT a "Google-hosted" site.

 

I get my email through Google Apps, yes, but those are MX records and have absolutely nothing to do with web traffic.  

 

The website is hosted on my Comcast Business Class connection.

Advocate

 • 

1.4K Messages

9 years ago

Your domain is hosted by Google.  I would recommend that if you want to Use your existing domain name with Comcast Business email and web hosting , please follow these instructions to accomplish this.

Gold Problem solver

 • 

610 Messages

9 years ago

Nah Rich, I don't think his domain was registered with Google. There are MX records pointing to Google mail servers, but the NS record for his domain shows references to "domaincontrol.com", which after a few seconds of digging turns up references to GoDaddy.

 

btw, OP the link you posted in your first post does not work for me - I get an "error 400 bad hostname". Your link included a single dot (.) at the end of the name; removing the dot causes the page to load. I also just tried http://50.253.68.225 and I got an IIS page. I am connecting from a Comcast business connection outside Nashville, TN.

New Contributor

 • 

7 Messages

9 years ago

Train, my DNS is hosted with godaddy, the website is www.CenterlineScores.com

There was a period there at the end because it was at the end of a sentence. No idea why the forum set up the link like that. The IP is correct but there are multiple sites hosted on that server so you have to use a domain name since that is what IIS is binding to.

Rich, all I can say is that this is not as simple as you think and I'm not as inexperienced with hosting as you think.

I'm just trying to understand why users from different parts of the country (some as far as California) who cannot get to the site from multiple different ISPs all have one thing in common, namely that the route to our server gets stopped at the same Comcast node just before it gets to my server.

Gold Problem solver

 • 

610 Messages

9 years ago

Was this a recent install? Only thing I can think of is that there is some mis-propogation between Comcast's backend CRAN/ibone, or that your route hasn't fully propogated.

 

If you set up a packet trace on the server while someone who can't access it tries to connect, do you see their connection attempt at all? Or do no packets reach you?

New Contributor

 • 

7 Messages

9 years ago

New Contributor

 • 

7 Messages

9 years ago

The one time we've been able to track this zero packets. No sign at all.