DNS scavenging and DNS Event ID 2502

I'm in the process of setting up DNS scavenging and I'm having some trouble.
In a test lab I have a Windows 2003 Standard R2 server with Active Directory
integrated forward and reverse zones. At the server level I configured
scavenging, and when I applied it, I specified for it to apply to all
existing zones. When I check the properties of the zones, scavenging is
enabled and the times specified at the server level are present. When I
manually run the scavenging operation from the server level, a 2502 error is
produced in the DNS event log, and no entries are scavenged. I checked the
Microsoft support article on 2502 and it doesn't seem to apply as the system
time when the scavenging operation is queued is beyond the "The zone can be
scavenged after" time shown in for the zone, and there are multiple records
whose "Record time stamp" indicate that they should be deleted. I have
waited over an hour in between manual scavenging requests as per the support
article for event 2502 but still have not had any luck. I would welcome any
information on this.

Thanks!

 

Hi
Did you compare your Scavenging definitions against the record time stamp?

--
I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services

 

Jorge,

I'm not sure if I'm clear on what you mean. When I look at the zone itself,
it says that the zone can be scavenged after 10/2/1:00PM. The No-Refresh and
Refresh intervals are both set to 7 days at the server level and scavenging
is enabled. At the zone level, scavenging is enabled, the no-refresh is
showing as 3 days, and the refresh is showing as 5 days. I have individual
records which are time stamped back on September 7th. If I advance the date
in my test lab to November 1 (well beyond the scavenge availability date, and
record dates) and I run a manual scavenge, I get a 2502 error in the DNS log.
I'm just not sure what's going wrong here, or what logging I can turn on to
get more information.

Troy.

 

When you enabled aging on the servers, these records already existed in DNS,
if I'm not mistaken the aging will only work for records created after aging
was enabled.

--

I hope that the information above helps you.
Have a Nice day.

Jorge Silva
MCSE, MVP Directory Services