General discussion

Locked

DNS doesn't resolve

By risaac ·
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 conversation is currently closed to new comments.

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

All Comments

Collapse -

DNS doesn't resolve

by Stillatit In reply to DNS doesn't resolve

It does sound like a DHCP problem with a lease not renewing, and the boxes thus not having a valid IP until you manually renew.

Things that might shed some light:

1. If you examine the DHCP database on the DHCP server while every station works, and then again when stations are not working, are all stations the same in the list?

2. When one W95 box stops being able to resolve, do they all, or is it random intervals for each client?

3. When a W95 box stops being able to resolve, if you do a winipcfg /all without doing a release or renew, are all settings as expected (or has the lease expired)?

4. When a W95 box stops being able to resolve, if you do a ping to some numeric address on the net, does it work? How about a numeric address on your LAN?

5. Are all clients pointed at the primary DNS first, or do some have the pair reversed?

Good luck.

Collapse -

DNS doesn't resolve

by risaac In reply to DNS doesn't resolve

Poster rated this answer

Collapse -

DNS doesn't resolve

by Raffi_ In reply to DNS doesn't resolve

HI. The fact that your non-MS boxes have no difficulty lead me to believe that the problem lies with the WINS. WINS is notoriously unreliable. Do you have a pointer to the DNS from WINS? I'll bet that you do. WINS seems to "lose" it's way over time.

If you have the NT 4 resource kit run WINSCHK and WINSCL to check for consistency in the WINS DB's

You might also try compacting the WINS db with the following command:

NET STOP WINS
JETPACK WINS.MDB TEMP.MDB
NET START WINS

Hope this helps . . .

Collapse -

DNS doesn't resolve

by risaac In reply to DNS doesn't resolve

The question was auto-closed by TechRepublic

Collapse -

DNS doesn't resolve

by wil In reply to DNS doesn't resolve

Raffi is exactly right! The OS's that work completely function on DNS resolution and no NetBIOS communication. Look at the node type resolution in your scope or global settings in your DHCP server. That determines what sequence order each client uses to resolve an address. Cache, WINS, broadcast, DNS, local lmhosts file. Your WINS is corrupt. Do what Raffi has suggested above. If you have multiple domains also consider the replication partners to your WINS servers. They too will need to be flushed. Recreating a WINS database is a no-brainer and typical pretty simple and straight forward. Just make note of any static assignments - which should be documented in your network documentation

Collapse -

DNS doesn't resolve

by risaac In reply to DNS doesn't resolve

The question was auto-closed by TechRepublic

Collapse -

DNS doesn't resolve

by wcraigmiles In reply to DNS doesn't resolve

Reverse the DNS roles to match the WINS roles.

Collapse -

DNS doesn't resolve

by risaac In reply to DNS doesn't resolve

The question was auto-closed by TechRepublic

Collapse -

DNS doesn't resolve

by risaac In reply to DNS doesn't resolve

This question was auto closed due to inactivity

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

Related Discussions

Related Forums