AD DHCP leases and renamed computers not be cleaned up.
Home > IT Answers > Networking > AD DHCP leases and renamed computers not be c...
EastCoastGuy
215 pts.
0
Q:
AD DHCP leases and renamed computers not be cleaned up.
DHCP, Active Directory, Windows Server 2003, DNS, DNS Updates, DNS Records
We currently rely on DHCP to update DNS.(Note: DNS Scavenging isn't enabled b/c it has removed needed records in the past).....

We often run into problems where renamed computers have their old computer name record remain in dns b/c the lease never actually expired. This creates tons of orphaned records in DNS.

Does anyone have a recommendation on how to fix this? It seems windows DHCP will only delete DNS records that expire normally.
ASKED: Mar 11 2009  7:31 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
Carlosdl
29855 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
The DNS update requests are issued by the client, and the DHCP server perform those updates on their behalf. When a client is renamed, it should request both, the creation of the new DNS records, and the deletion of the old DNS records.

The server can be configured to perform DNS updates regardless of whether the client requests this action or not. You could try this, to see if it helps.

To modify this setting, select the Enable DNS dynamic updates according to the settings below check box and click Always dynamically update DNS A and PTR records, which is located in Properties on the DNS tab on the applicable DHCP server or on one of its scopes.

Another possibility, if you have more than one DHCP server, is that one DHCP server creates the DNS records (and thus becomes the owner of the name), but later when a DNS update is requested for that client, if for any reason the owner DHCP server is not available, no other DHCP server can update the records, because they are not the owners of the name.

If that is the case, the problem could be solved by adding all DHCP servers as members of the DnsUpdateProxy built-in security group, but this involves other security-related issues.

Here's a Microsoft document that explains some of these topics in detail.
Using DNS servers with DHCP
Last Answered: Mar 12 2009  2:05 PM GMT by Carlosdl   29855 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Troy Tate   0 pts.  |   Mar 11 2009  7:37PM GMT

What is your lease time? About 8 hours is a good length. Clients will begin to renew the lease around 4 hours. Printers and other devices that are on all the time can have longer leases.

 

EastCoastGuy   215 pts.  |   Mar 13 2009  1:28PM GMT

The settings to allow dynamic updates to DNS and discard A and PTR records is enabled. The DHCP lease time is set to 3 days.

This problem seems to happen with renamed clients. A common example is imaged computers that have temp names and are then renamed.

 

Carlosdl   29855 pts.  |   Mar 13 2009  1:46PM GMT

and, do you have more than one DHCP server ?

 

EastCoastGuy   215 pts.  |   Mar 23 2009  8:43PM GMT

We have 3 AD DHCP servers. It’s a basic site setup in AD where each site has a local DHCP server.

 
0