Home | Site Map | Cisco How To | Net How To | Wireless | Search | Forums | Services | Donations | Careers | About Us | Contact Us|
|
|
Home | Site Map | Cisco How To | Net How To | Wireless | Search | Forums | Services | Donations | Careers | About Us | Contact Us| |
[
Home |
Contents |
How To Discussion |
Archive |
Search |
Post
|
Reply
| Next
| Previous
|]
From: Date: 06 Nov 2006 Time: 00:21:53 -0500 Comments: 1. Incorrect forwarder address in the internal DNS, for example, your ISP changed the DNS address. Or you can try to turn off the forwarder. 2. Make sure if you have multiple DNS servers that they are not forwarding to each other. They should forward to an ISP's, or if a child domain in a delegation scenario, to forward to the parent, then the parent forwards to the ISP. 3. Check this article: Description of the DNS Server Secure Cache Against Pollution setting, http://support.microsoft.com/?kbid=316786 4. If you also receive email non-deliverable notifications, you may want to open each queue containing a postmaster message to a spoofed address and delete it (without NDR). Then clear the DNS cache. 5. Poor Internet connection. 6. If the packet is from a private IP address, you may have some hosts with illegal characters in their names. 7. This problem may occur because Windows Server 2003 does not support DNAME.
|
|
|
This web is provided "AS IS" with no warranties.
Copyright © 2002-2009
ChicagoTech.net,
All rights reserved. Unauthorized reproduction forbidden.