Web Hosting with GoDaddy

[Penth]

I don't know if this is the best forum to ask in but I need help pretty badly and quickly.

I've got a dedicated server setup with GoDaddy but I've had some customers calling lately saying my site doesn't work.

you can see the problem at http://www.ziggosfifties.com.

If that pulls up fine then you are probably not affected (I'm not so it is very tough to troubleshoot this. It comes up just fine on my computer here at home and at work.)

If it comes up without stylesheets and images and none of the links work then you are seeing what I'm hearing some other people are seeing. One of my coworkers was in the hospital and accessed our site through their network and was able to see it so I know what it looks like instead of just a couple of customers saying it doesn't work.

I'm guessing it has to do with the resolver and these subdomains aren't being resolved properly, but I don't know anything about setting up a resolver right. If anyone has any clue what to do about this and can give me a hand it would be very greatly appreciated.

 

[simondedalus]

you can visit wetpaint.com

 

[MichaelD]

Nice website. Comes up fine for me. I'm guessing it's a problem with the customer's PCs not having the proper IE updates, Flash plugins or whatever.

 

[cleverhandle]

Unless you've changed your DNS settings recently (i.e. last 48 hours or so), I don't think it's a name resolution problem. If one computer resolves your site's names correctly, then the others will too. Sounds more like a browser compatibility issue to me.

If you *have* changed your DNS setting recently, then maybe they just haven't propagated yet. Not much you can do then but wait.

 

[RebateMonger]

I have no problem bringing up your site.

Run http://DNSReport.com against your domain name and see if there are any errors. Being a very lazy consultant, that's what I do first when there are Domain or DNS issues. Then I'd dig into http://DNSStuff.com's other tools.

 

[Penth]

Originally posted by: RebateMonger
I have no problem bringing up your site.

Run http://DNSReport.com against your domain name and see if there are any errors. Being a very lazy consultant, that's what I do first when there are Domain or DNS issues. Then I'd dig into http://DNSStuff.com's other tools.

Thanks for your help. Like I said it is a difficult problem to track down because it's so random. I'm pretty sure it's not a problem related to the computers accessing the site because the computer that accessed the site at a hospital has also accessed it fine from our internal network. It worked fine on our network and not at all there at the hospital.

I ran a report from dnsreport.com and it came up with a few failures:

FAIL Missing (stealth) nameservers FAIL: You have one or more missing (stealth) nameservers. The following nameserver(s) are listed (at your nameservers) as nameservers for your domain, but are not listed at the parent nameservers (therefore, they may or may not get used, depending on whether your DNS servers return them in the authority section for other requests, per RFC2181 5.4.1). You need to make sure that these stealth nameservers are working; if they are not responding, you may have serious problems! The DNSreport will not query these servers, so you need to be very careful that they are working properly.

ns2.ip.secureserver.net.
ns1.ip.secureserver.net.
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).

FAIL Missing nameservers 2 ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
ns1.ziggos.com.
ns2.ziggos.com.


FAIL Stealth NS record leakage Your DNS servers leak stealth information in non-NS requests:

Stealth nameservers are leaked [ns2.ip.secureserver.net.]!
Stealth nameservers are leaked [ns1.ip.secureserver.net.]!

This can cause some serious problems (especially if there is a TTL discrepancy). If you must have stealth NS records (NS records listed at the authoritative DNS servers, but not the parent DNS servers), you should make sure that your DNS server does not leak the stealth NS records in response to other queries.



There is also a single point failure but I'm aware of that one and don't really intend to do anything about it for now. It seems like those nameserver failures could be causing this type of a problem.

I don't know if you've ever used cPanel before but my resolvers were set to IP addresses that didn't return a response and some other settings were set to an IP address from my old server. I don't have any idea how that would have happened.

I changed DNS settings after this had been happening so hopefully it gets fixed. Before when I tried to ping NS1.ziggos.com it would go to something like 208.109.107.108 which was my old IP and now it seems to be going to the right place.

I guess I'll just wait and see now unless you have any tips on those failures that were reported. Thanks in advance.