Share via

Forum FAQ: DNS records are deleted automatically from DNS server.

Question

Monday, February 22, 2010 8:48 AM

Symptom

 

Some DNS records may be deleted from DNS server automatically. For example, you have created static A records for your printers.  However, these records are deleted automatically.

 

Cause

This problem may occur when DNS scavenging is enabled. DNS scavenging is feature which helps remove stale resource records automatically. Scavenging improves DNS server and zone transfer performance when working with dynamic update together. However, some devices may not be able to perform dynamic update. When DNS scavenging is enabled, these records may be recognized as stale and deleted automatically because they are not updated timely.

 

Solution

Scavenging is set in three places on a Windows Server:

 

1.                   On the individual resource record to be scavenged.

2.                   On a zone to be scavenged.

3.                   At one or more servers performing scavenging.

 

It must be set in all three places or nothing happens. You may configure DNS scavenging settings based on your requirement.

 

Option #1: Disable scavenging on the individual resource record

If only several specific records, such as A record for TCP/IP printers, do not support dynamic update and you want to enable DNS scavenging on other records, you may disable scavenging on these particular records by performing the following steps:

 

1.                   Open the DNS snap-in.

2.                   Right click the individual record and open the Properties dialog.

3.                   Uncheck the Delete this record when it becomes stale option and click OK.

 

Option #2: Disable scavenging on the DNS zone

If you want to disable DNS scavenging on a particular DNS zone, you can perform the following steps:

 

1.      Open the DNS snap-in.

2.      In the console tree, right-click the applicable zone, and then click Properties.

3.      On the General tab, click Aging.

4.      Clear the Scavenge stale resource records check box.

5.      Click OK.

Option #3: Disable scavenging on the DNS server

If you want to disable DNS scavenging on the server as a whole, you can perform the following steps:

 

1.                   Open the DNS snap-in.

2.                   Right click the DNS server item and open the Properties dialog.

3.                   On the Advanced tab, clear the Enable automatic scavenging of stale records option, and click OK.

 

More Information

 

Using DNS Aging and Scavenging

http://technet.microsoft.com/en-us/library/cc757041(WS.10).aspx

 

Don't be afraid of DNS Scavenging. Just be patient.

http://blogs.technet.com/networking/archive/2008/03/19/don-t-be-afraid-of-dns-scavenging-just-be-patient.aspx

 

Applies to

 

  • Windows Server® 2003 operating system
  • Windows Server® 2008 operating system
  • Windows Server® 2008 R2 operating system

All replies (4)

Monday, July 18, 2011 11:37 AM

 

I have created one STATIC DNS Entry, for Example "ROSE" and

 

1.                   Open the DNS snap-in.

2.                   Right click the individual record (ROSE) and open the Properties dialog.

3.                   Uncheck the Delete this record when it becomes stale option and click OK

 

For the moment the time stamp will show as BLANK

 

 

Then I logged in to server "ROSE" and restarted DHCP Client Service on server or restarted server, the time stamp is automatically setting as current date and "DELETE THIS RECORD WHEN IT BECOME STALE" check box also selected automatically

 

and gets deleted after a week or so when the scavenging runs

**Is there any way to avoid the static entries become dynamic automatically. **

 

Domain Controller or DNS OS is Windows server 2003 R2 Standard Edition SP2

 

Thanks & Regards

Dinesh Cholekkavil

**
**

Tuesday, July 19, 2011 12:12 AM | 1 vote

 <snipped>

**Is there any way to avoid the static entries become dynamic automatically. **

 

Domain Controller or DNS OS is Windows server 2003 R2 Standard Edition SP2

 

Thanks & Regards

Dinesh Cholekkavil

**
**

 

Static entries for the most part, are used for additional hostname records for a specific machine. For example, webserver01 is the hostname of a machine under the domain.local zone with an IP of 192.168.10.80. I can also create a www hostname record and provide the same IP of 192.168.10.80. THis way when someone types in www.domain.local, they'll get sent to 192.168.10.80.

If you want to prevent the record from becoming a dynamic record, don't use the same name as the server, or disable Register This Connection in the server's NIC properties for that interface. Of course this setting does not stop a domain controller, which registration of records is controlled by the Netlogon service, which is a different topic.

Ace

Ace Fekay
MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php

This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Tuesday, December 31, 2013 11:50 AM

Hi

Ace thanks..

Can I get the link for

Of course this setting does not stop a domain controller, which registration of records is controlled by the Netlogon service, which is a different topic.

Wednesday, June 14, 2017 1:49 PM

what is the Event ID for AD DS 2012 Machines.. I am not finding in any forums..