Since when you log off the wireless, you're NOT actually releasing the address, the DNS server is keeping that address -- as you have pointed out, for the term of the DHCP lease, or 7 days.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... you need to setup Dhcp advanced DNS options to Always dynamically update DNS A and PTR records Also you must set credentials in DHCP server properties, other wise this process will not work This will ensure that when DHCP lease will expires \ changes by any mean on DHCP server, it will update corresponding DNS records Also you need to set DNS scavenging in such a way that no-refresh interval must be set to (half) less than refresh interval This will keep DNS server open for accepting dynamic update more time Also ensure that secure dynamic update is enabled on DNS zone Check below article to understand scavenging process correctly and to identify its relation with DHCP To setup scavenging Mahesh I had the dynamic update and DHCP credentials already in place.Any help would be great, if you need more details let me know.
OK Every half hour the lease will try to renew by machines itself Because generally client will try renewal after half lease time elapsed Now Even if you keep No refresh (1 HR) refresh (2 HRS) = 3 HRS, scavenging will run every 3 HRS and it will delete records older than 3 HRS Most of the records are updated every half an hour, hence scavenging will not delete most of the records Is there any specific reason for keeping such a short duration, if you could please explain... Please set your DHCP advanced DNS options as below so that your DNS records will get updated Also add DHCP server to DNSUpdate Proxy Group on Domain Controller (DNS Server) You already have set credentials in DHCP console Mahesh I inherited the setup and am in the process of trying to clean up some of the previous admins configurations. The DHCP lease times have been reduced to 1 hour for each VLAN.
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. 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.
Once your wireless DHCP server drops the address, it should remove it from the DNS server, thus allowing the DNS ADD request from the wired VLAN DHCP server to succeed -- and your name recognition should work (at least most of the time). Dan IT4SOHO If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. 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 _msdcs.zone 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.
I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing.
Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S. 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.