I believe WUG attempts to do a lookup of 127.0.0.1, but I don't know if they are using the MS stack or doing it with their own code. The difference here is that in the real world, when you do a request, the machine will do several (I think 3) attempts before failing and trying any secondary server identified. And the time between those re-attempts is fairly long.
If WUG is doing it's own thing (which I believe it is), attempts once and gets a failure, it may show up as a failure to WUG but the rest of the world is working but possibly with repeated attempts not noticed by the user.
When WUG is saying it's not working, perhaps it would be wise to go into the tools section and do a lookup with the WUG machine so you're using the same machine as a comparison.
I do not see DNS failures, but I am only two routers away via 100 meg links and my servers are Sun machines.
I do see occasional failures of POP, and when I get them we find the mail machine is overloaded.
For those encountering the failure of DNS, have they increased the timeout with any success?
At 09:07 AM 3/13/2003 -0700, you wrote:
>We have a few DNS servers throughout our global network that I am monitoring from Atlanta. I keep having issues with DNS timing out and sending out false positives. I am monitoring the point of entry and I can actually do DNS queries from the servers when WUG thinks it is down. Anyone have any idea s? Thanks!
I may be having similar issues. One of my boxes repeatedly fails to locate two servers in another building (which it needs DNS to find). Several other boxes can see them fine. Is WUG doing anything strange with DNS or traceroute?
This communication is intended for the use of the recipient to which it is addressed, and may contain confidential, personal and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communication received in error, or subsequent reply, should be deleted or destroyed.
