DNS doesn't resolve - TechRepublic
General discussion
May 2, 2001 at 09:43 AM
risaac

DNS doesn’t resolve

by risaac . Updated 24 years, 11 months ago

I have a primary and secondary DNS server running on WinNT4 server(SP6a). (These also happen to be my primary and secondary WINS servers, except their roles are reversed in the latter capacity.)

The majority of my desktops use Win2k, but we do have a few Win9x, MacOS, and even a couple of Linux server.

Problem: Every few days, the Windows computers (2k and 9x) can no longer successfully resolve to an intranet website.

For example, internalsite1.mycompany.com with IP 192.168.1.10 will load on their web browser (IE5+ or Netscape6)without fail for a few days. But, for some odd reason, it will suddenly stop loading.

If I attempt a ping, i get an unknown host error. If I perform an nslookup on the same FQDN I get a response back of192.168.1.10; using the very same machine that could not one second ago load the page in their web browser.

During this time the MacOS, Solaris8 and Linux all load up the site without fail.

If I release and renew the ip (DHCP), the system invariably loads the page.

As a test, I added a new A record for a new server (no web serving, just a linux db server) into MSDNS. Immediately the Mac, Solaris, and linux boxes could resolve this name; confirmed via pinging. The windows boxes could not until we released and renewed their IP.

Where in this conflaguration lies the problem? 1)Definately not the server because other OS’s resolve the name. 2) not the browser because netscape and IE WILL load the pages after a refresh (could it be aDHCP issue? not likely i think) WINS appears to work across the network; no errors reported in my Event Logs.

ANYONE have any suggestions?

This discussion is locked

All Comments