Hello,

We have a mix of 3 Windows 2000 DCs and 2 Windows 2003 DCs. Each W2K DC is
located at it's own site and the two W2K3 DCs are on a fourth site. One of
the Win 2000DC has the five FSMO roles and another Windows 2000 DC is the
only DNS that has scanenging enabled for stale records. The scavenging cycle
is 6 hours.

The problem is the property called 'delete this record when it becomes
stale' gets checked every 2-3 days for the Windows 2003 DCs and the next
scavenging cycle deletes these DNS entries, both A and PTR records. We start
having replication errors since the other DCs can't locate the 2 missing
ones.

Do you have an idea about this problem?

In news:(E-Mail Removed),
Niveau3_TLB <(E-Mail Removed)> typed:
> Hello,
>
> We have a mix of 3 Windows 2000 DCs and 2 Windows 2003 DCs. Each W2K
> DC is located at it's own site and the two W2K3 DCs are on a fourth
> site. One of the Win 2000DC has the five FSMO roles and another
> Windows 2000 DC is the only DNS that has scanenging enabled for stale
> records. The scavenging cycle is 6 hours.
>
> The problem is the property called 'delete this record when it becomes
> stale' gets checked every 2-3 days for the Windows 2003 DCs and the
> next scavenging cycle deletes these DNS entries, both A and PTR
> records. We start having replication errors since the other DCs can't
> locate the 2 missing ones.
>
> Do you have an idea about this problem?

I would leave it at the default 7 days. 2-3 days is way too short.
Otherwise, this may not be scavenging related. If you disable scavenging, do
the replication errors disappear?

--
Regards,
Ace

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT,
MVP Microsoft MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations