Quantcast
Channel: Directory Services forum
Viewing all articles
Browse latest Browse all 31638

Understanding XP and Win7 client DNS updates

$
0
0

Hi,

I'm trying to understand how some of the DNS registration updates work between Domain member client PC and the AD infrastructure when not on the local LAN, but on a routed LAN.

I've a simple 3 DC (no RO DCs) setup. On my LAN the DHCP server updates DNS entries for clients. The DNS servers are setup only for Secure Updates.  I'm not aware of any GPO settings overriding default setups.

However we now have an off-shoot LAN, that has its only Linux DHCP server.  Clients on that LAN are pointed to our normal DNS servers directly. There are no firewalls involved, only IP routing.

What we see, is that if an existing record exists when a client PC moves from my LAN to the off-shoot LAN, then its DNS entry is not updated. However, if the client doesn't exist in DNS (because I delete it manually), then they can register in ok from that new LAN.

I don't see this in my local DHCP/DNS update mechanism. Only with the new LAN.

I know that DNS registrations are done by the DNS Client on the PC, but I'm not sure what else is taken into account when security checks are made.

Also, I'm seeing 'stale' entries in the DNS listing. Scavanging is set for 7 days, but yet I see timestamps for 30 Nov, 29 Nov, 28 Nov etc..

Any advice on how to proceed appreciated.  I've searched for basic DNS and read various articles, so I think my understanding is good, but can't see why the clients aren't updating:

http://technet.microsoft.com/en-us/library/cc784052(v=ws.10).aspx
http://social.technet.microsoft.com/Forums/lv/winserverNIS/thread/8f5310f6-3c8e-47c2-a95f-07c4f0ea19d0


Viewing all articles
Browse latest Browse all 31638

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>