Reverse Zone is getting cluttered

  • Thread starter Thread starter Benito
  • Start date Start date
B

Benito

Reverse zone has some very old entries and multiples of
many DHCP clients at different lease addresses from
different lease times and is more often returning bad
(old) data. Forward zone seems to be very clean and is
always returing correct data.

What should my zone no-reresh, and refresh settings be at?
In order for Zone scavenging of stale resource records to
work must the "enable scavenging of all stale records" be
checked on the DNS server properties?
Would enabling the server scavenge help my situation and
at what interval considering the configuration below?

Thanks a million

DHCP Server and only Scope -
Lease period 8 hours
Auto update DHCP client info in DNS? Yes
Always update DNS? Yes
Discard forward lookups when lease expires? yes
enable updates for non supporting clients? yes

DNS Server -
Enable automatic scavenging of stale records? No
DNS forward Zone -
AD Integrated, Allow dynamic updates? Yes, Scavenge stale
resource records? yes, refresh int=15 min, retry=10 min,
expire=1 day.
DNS reverse Zone -
AD Integrated, Allow dynamic updates? Yes, Scavenge stale
resource records? yes, refresh int=15 min, retry=10 min,
expire=1 day.
 
In
Benito said:
Reverse zone has some very old entries and multiples of
many DHCP clients at different lease addresses from
different lease times and is more often returning bad
(old) data. Forward zone seems to be very clean and is
always returing correct data.

What should my zone no-reresh, and refresh settings be at?
In order for Zone scavenging of stale resource records to
work must the "enable scavenging of all stale records" be
checked on the DNS server properties?
Would enabling the server scavenge help my situation and
at what interval considering the configuration below?

Thanks a million

DHCP Server and only Scope -
Lease period 8 hours
Auto update DHCP client info in DNS? Yes
Always update DNS? Yes
Discard forward lookups when lease expires? yes
enable updates for non supporting clients? yes

DNS Server -
Enable automatic scavenging of stale records? No
DNS forward Zone -
AD Integrated, Allow dynamic updates? Yes, Scavenge stale
resource records? yes, refresh int=15 min, retry=10 min,
expire=1 day.
DNS reverse Zone -
AD Integrated, Allow dynamic updates? Yes, Scavenge stale
resource records? yes, refresh int=15 min, retry=10 min,
expire=1 day.
Click to expand...

Enable scavenging to clean them up.
:-)

Sometimes if DHCP added them in there, they won't scavenge and need to
remove them manually.

You can try (from a previous post in this forum):
Run the following command to timestamp all records (including manually
added records): dnscmd /AgeAllRecords example.com @ /tree /f

This will age all records so after you run the above command,

--Uncheck "Delete this record when it becomes stale" for records you
want to keep.
Click to expand...


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top