General discussion

Locked

Intermittent DNS Failure

By amykong30 ·
I?m running Windows 2000 Server. I believe I suffer from some kind of virus network event, but I don?t what it was. Seemly unrelated and probably unrelated failure happened all within a few days of one another. First my ability to browse the network, or any network drives came to a stand still. A snap server NAS completely failed. A monitor burned out, and an AGP network slot creates a yellow tinted screen. With some graphic cards, but not others. Though none of these problems have really been solved, the primary problem at this time is DNS.

My server is running IIS, sql server, exchange server 2000 and serves as my local domain controller (PDC). I have an Efficient Network router and DSL modem, running DHCP and NAT (routing only 4 ports to the server). The server is running DNS, which appears the configured properly with forward and reverse lookup zones ? it worked perfectly before, and I have changed nothing. Now what happens is within a certain time of rebooting the server, from 1 to several hours both my server and other boxes on the network are unable to resolve many, but not all domain names. This causes problems in browsing and sending emails. The domains that resolves and fails are not consistent. I can go to any site with an IP Address. There are no DNS error being generated in the Event Viewer.

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by Aakash Shah In reply to Intermittent DNS Failure

Have you ran a virus scan on your network to detect any viruses? Also, I have experienced spyware and adware that has caused problems when you attempt to remove them and they mess up DNS. TechRepublic ran an article (it is now TechPro Gold) about this titled "Use these techniques to fight back against spyware" and discussed how WinSock may have been broken.

Collapse -

by curlergirl In reply to Intermittent DNS Failure

Your problem may be related to the fact that you're running DHCP on the router and DNS on your server. Or, it might even be that you are running DHCP on both without realizing it and they are conflicting. The ideal configuration would be to be running DHCP and DNS on the server rather than splitting them up. What might be happening is that the DHCP server on the router is handing out the wrong DNS server information to the clients, and/or if DHCP is running on both the server and router, one or both of them are mis-configured. You DO NOT want DHCP running on both; ideally it should be running on your server only, and not on the router at all. All of your internal clients should be set to use your internal DNS server, not an external server. So, first check to make sure that DHCP is not running on both the router and the server. If it is, turn DHCP OFF on the router and let the server handle it all. Also, make sure whichever DHCP server is running, it is assigning ONLY the internal DNS server address to the clients, not an external one.

If that fixes the problem, then we have identified it correctly. If it doesn't, then we have at least eliminated one possible cause.

If the DNS settings are already correct, then you should check to make sure that your DNS server is not configured as a root server. If it is, remove the root component (labeled (.) in the forward lookup zone). Then, also be sure that your DNS server is set to use forwarders. The forwarders would be the ISP's DNS servers.

Hope this helps!

Back to Networks Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums