Discussion Locked

DHCP and DNS

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We are running NT4 server with W2K professional clients. DHCP is running on a NT4 box as well as a internal DNS server. Included in the DHCP scope is our internal DNS server ISP's DNS servers.

The problem we are having is when ever an update ismade to our internal DNS entries, it requires the client to renew their ip address before they are able to see the change.

Doing an nslookup before the renew of the ip address shows the correct change. However pinging that same entry does not work. It returns the "unkown host error".

Any ideas?

5 replies

by bwheel

W2k professional seems to do more caching with the DNS entries that it recieves, you said that whenever you make a change in your DNS servers entries, the change is not reflected on the workstation. I think what is going on is that the DNS entry iscached on the workstation and is not updated. The command to flush the cache in w2k is ipconfig /flushdns. When you do an nslookup, the entry is given direct from the server, and I am not sure whether or not the new entry is compared with cache. My guess would be that the ipconfig /renew flushes the dns cache, as you might be moving to a new network, or new ip address scheme. There might be a way to shorten the length that the dns entry is cached. I seem to remember w2k dns server as having a setting for that. If you do this, you will increase traffic, but not by a large amount. Try looking for a workstation setting first.

by dforcey

Here's what I would do: While you're in the DHCP Manager on your NT 4.0 Server, (you're in there changing the DNS settings anyway) open up the scope properties and change the Lease Duration to something real short (15 minutes). Leave the setting like that for a day. Then set it back. The more often you make DHCP changes, the shorter your lease duration should be set to.

This discussion is closed to new replies.