M
Marlon Brown
In my organization folks run an application that performs reverse nslookups
and in the past my vast large of mobile clients returned lots of duplicated
records.
Then on my DNS settings I did:
Scavenge old records=1 day
I kept the "Forward Lookup Zones" as refresh interval=7 days, no-refresh=7
days.
DHCP server lease=1 day
In the "Reverse Lookup Zones" I set
interval=1 day, no-refresh=1 day.
That apparently tool care of the problem.
Question is this, imagine I want to increase the IP Lease Expiration on
DHCP=8 days. Note that that I am deleting the reverse records very often now
(2-3 days).
Any problem deleting Reverse lookup zones more often (3 days) than deleting
the Forward Lookup Zones (14 days) ?
I want to make sure that I don't end up having problems in case my domain
controllers go down on remote sites or deleting legitimate records out of my
DNS.
As far as I know it is OK deleting Reverse Lookup Zones more often since AD
doesn't rely on that.
and in the past my vast large of mobile clients returned lots of duplicated
records.
Then on my DNS settings I did:
Scavenge old records=1 day
I kept the "Forward Lookup Zones" as refresh interval=7 days, no-refresh=7
days.
DHCP server lease=1 day
In the "Reverse Lookup Zones" I set
interval=1 day, no-refresh=1 day.
That apparently tool care of the problem.
Question is this, imagine I want to increase the IP Lease Expiration on
DHCP=8 days. Note that that I am deleting the reverse records very often now
(2-3 days).
Any problem deleting Reverse lookup zones more often (3 days) than deleting
the Forward Lookup Zones (14 days) ?
I want to make sure that I don't end up having problems in case my domain
controllers go down on remote sites or deleting legitimate records out of my
DNS.
As far as I know it is OK deleting Reverse Lookup Zones more often since AD
doesn't rely on that.