I have one hosting customer in Western Canada who regularly sends me email saying that he gets a Gateway Timeout when he tries to point his browser to his site. In fact, if I give him a list of some of my own sites that are on the same server, het gets the same message. Yet at the very same time this is happening, I am able to access the sites. Sites are functional, server is up, everything seems fine. Except that he keeps getting the DNS error...
And if he pings or does a tracert, everything seems OK. But still gets error.
Can someone please take a crack at explaining why/how this happens?
DemoDemo.com - Flash tutorials since 2002 DemoWolf.com - 5,300+ Flash tutorials for hosting companies, incl. Voice tutorials
Hi - when it happens again ask him to try and access his (your) sites by their IP address, if sucessful it shows it is a DNS problem, if it still fails then it isnt - but you will then be at least one step ahead of where you are now and know where to carry on looking :-)
Could also be a problem with his isp, hence the 'gateway' part of the error, maybe they dont have a good working route to your server(s)? or they are having dns issues like mentioned above. If you like, post a sample ip/domain in here and well see who can access it and who cant
Hi - I think your problem is with the name servers ns1 & ns2..waterhosting.com which do not appear to have entries in the waterhosting.com zone file because if you do a 'dig ns1.waterhosting.com' you do not get an answer.
Hi - no I am not saying that WHM has done anything wrong, but your name servers are not setup quite right. When you do a DNS lookup for any domain it should return the IP address, so when you issue a command to do a DNS lookup such as....
... an IP should be returned, but when I tested the above an IP was not returned for the name servers and it should have. This is the only problem I saw with the DNS and I am not sure that this is your problem, but as it is wrong it just may be ???? Anyway IMO it is best to get this fixed and see if the problem remains or not.
To fix this you will need to add the following entries to the waterhosting zone file...