Strange DNS Issue

[MQCarpenter]

Every once in a while, we come upon a site that we get DNS errors on. It later works, but for that moment, our internal DNS can not determine the site. We can however, get to the site via IP. I know that is very general, but has anyone seen something similar? ------------------------

"We are all ignorant about one subject or another. Most of us just can't keep our mouths shut when that topic comes up."
~Anonymous

 

[ShackDaddy]

It's probably a temporary failure of the remote DNS server that your server is querying.

I have had a weird thing happen with a late beta (or first release) version of Windows2000 Pro though. Sometimes I could get to a site, with the same error that you are getting. I would then go to a command line, ping the site by FQDN, and it would work. Then I would try it in my browser again and it would be fine. It was like the DNS resolver that my browser was using had problems, but the one that the command-line triggered didn't. After I'd ping it, the resolution would be cached, and I wouldn't have trouble with that site. This would happen around 30% of the time, but I haven't seen it lately, perhaps due to a service pack fix.