Has anyone had domains you are hosting that previously worked fine, and then suddenly just stop for a bit, then work again, etc? I have, and everything seems to be perfectly set on our systems. During the times a domain is down, I do a whois on it on Netsol and it always returns for the first line:

> >Registrar request timed out. Could not connect.
> >Whois Server Version 1.3
etc, etc

It seems to be OpenSRS registered domains that are doing this. Is it possible there is a problem above us, maybe at the main registry servers or whatever? I cant find anything out of whack on our systems, and this is the only other thing giving me any kinds of hints...

Hmm strange.... I never had anything like that happen. Well as far as my knowledge goes. Nobody I ever hosted reported something like that and our monitoring didn't report anything similar.

We get that all the time. It turns out you can just use other whois providers, etc. Take for instance NameCheap, their information from VeriSign comes up with a timeout, also with Doster ... usually. You just have to find out who the main provider is. With some looking though a host should be able to find it but that's not always the case.

Many whois servers are often overloaded or unreachable at times, but it's irrelevant.

The whois server is not accessed when reaching an address by domain name. Only the root servers and DNS servers are involved.

You might try doing a dig on the domain name when you're experiencing the problems.

hmm, well I am having one helluva time figuring this one out. Domains are up, then down, then up again.. I'm sure that's it's in the dns somewhere, but everything looks fine.... even my forums are down right now. I changed the IP on it, and everything points to the new ip...but browser still tries to goto old IP even though all files show the new IP. #$@#$ dns....

What is the domain in question?

If it is on the same dns server as the domains listed in your signature.... You have a mess.

out of 4 different NS entries for the domains, not all of which have the zone files consistent with the glue records, one of the nameservers doesn't appear to be listening, one is refusing connections, one is returning invalid data, and I quit looking at that point. :)

Now... the domains you are referring to may not be any of those three, as none of them seemed to have anything to do with OpenSRS for the registrar, so this may be totally unrelated to the problem you were talking about. I just thought it was kind of curious.... and maybe related to the problem.

Well, it's interesting to note that Netsol and other whois show different records for our dns4com.net nameserver... this is driving me crazy. I have made a number of changes in our own files to test out things, and they make absolutely no difference whatsoever...

Actually Webdude I am having the same problem with a few of my clients. :eek:

They can see about half ot the domains hosted on the server and then the other half they can't or at times they can see all of them and then sometimes only one is having the problem. It jumps bakc and forth from being online and offline, I know eveyrthing is setup correctly and the servers haven't been offline cause everythign is being monitered. I emailed godaddy to see if the nameservers maybe weren't propagated correctly when they set them, but they just say that it's not them it's me. :(

I would have to switch from ISP to ISP to check this out ... even though all domains have been on the servers and propagated for over 2 weeks now, to I know that the ISPs have the information in ther network .... but I am still stumped! :confused:

hmmm..... I get the same answer for `whois dns4com.net` from NetSol and OpenSRS. both list ns.dns4com.net and ns2.dns4com.net as the nameservers. The root nameservers also have it that way, and all of them point to 216.187.101.27 (which is un-reachable) and 216.187.101.28 (which is refusing connections on port 53).

So.... there is not much chance of reaching any web site which relies on those two nameservers.

Added to previous post.....Which includes worldzonesupport.com as it is supposed to be using the ns/ns2.dns4com.net nameservers, which are not talking to outsiders. :) Which means nobody can get to your forums.

I am a little lacking in DNS knowledge. I'd be willing to pay a reasonable fee to have someone fix this mess for me. Simply let me know...

sent you a PM

Yaeh I got it. Thanks. Was about to go respond to it. Am writing the response now..

Hi webdude,

I have the same problem you had. The domain is up and going fine then suddenly it is not reachable. I hope it comes back soon but I do not know why is this happening. Did you know what the problem is?

Does anyone know why this happens?

Thanks.