gaydatingpro com - Windows clients not updating dns records

Let me know if you need any further information Ok Great.

I am running a Windows 2008 R2 domain with Active Directory integrated DNS.

All users have laptops and frequently switch from wired to wireless connections (these are on separate VLAN's).

I stumbled upon the following topic ( where The behavior of Client not registering PTR record by default is modified prior to Windows7 (mostly during Vista time) and is the intended behavior.

The Dhcp Server is responsible for performing PTR record registration on behalf of client.

For the zone in question i have refresh interval of 15 minutes, retry 10 minutes, expiration 1 day, TTL 1 hour. I had most of that in place but did find the DHCP lease time for the wireless scope was set to 7 days and Name Protection was not enabled.

I have set this to match the wired scope for lease of 1 day and Name Protection enabled.You say there are separate VLANs for the wired and wireless networks -- if that also means there are separate DHCP servers, then you're especially in luck... The main point you mention though is setting the wireless lease time to 15 minutes. I modified the DNS scavenging to No-refresh = 1 hour Refresh interval = 2 hours I will keep you posted on the results as I am still experiencing the issue but just made this change.most locations with lots of wireless users set a DHCP lease time of 15 minutes (vs. The issue being, with a 1-day lease, assuming a 24-bit netmask, you can only allow connections from 253 users per day -- regardless of how many at once. You have kept very tight refresh and no refresh interval Ensure that your domain DNS zone srv records are updating as appropriate Other wise scavenging process will eventually delete all those srv records as well under and zone (_TCP, _UDP, _MSDCS folders etc.) I'd keep refresh interval 8 HRS and No refresh interval 4 HRS as a precautionary measure so that you will get sufficient time to update all relevant SRV records on domain controller Remember, scavenging need to be enabled on only one DNS server and changes will get replicated to all other DNS servers (which are also domain controllers) Mahesh I have made the suggestion to set the refresh intervals to the times above.As the DHCP servers in this environment are Linux based we would like the clients to update their PTR records themselves.Updating the PTR records means a client registers his name and IP in the reverse lookup zone.However in the past I have seen strange behavior with the GPO settings below Administrative Templates\Network\DNS client section, and today was just the same. Below Computer Configuration DNS Client there is a setting called “Register PTR Records”.

Tags: , ,