DNS scavenging concerns

  • Thread starter Thread starter donkenheimer
  • Start date Start date
D

donkenheimer

We've got 2 Win2k3 DCs, on a single domain. We have about 250 users on the
(local area) network, w/ just 1 class B subnet.

Scavenging is not turned on and we've got lots of stale/duplicate IP
records. We've been hesitant to activate scavenging because we are worried
about possible pitfalls.

One such problem I've read about is the refresh and no-refresh intervals
being too short. What would be a good setting?

What about statically assigned IPs, such as those belonging to servers?
Would they get scavenged too?

Any other conceivable problems we haven't thought of?

Thank you in advance.

=====
 
Make sure your scavenging period is longer then your DHCP lease time.
Manual DNS records will not be scavenged.

The draw back I've seen is where DCs sporadically did not update their DNS
records and got scavenged. net stop netlogon and net start netlogon solved
the problem.

--
Kind regards,

Erik Cheizoo
eXcellence & Difference - we keep your business running
============================================
Always test in a non-production environment before implementing
Guidelines for posting: http://support.microsoft.com/?id=555375
============================================
 
donkenheimer said:
We've got 2 Win2k3 DCs, on a single domain. We have about 250 users on the
(local area) network, w/ just 1 class B subnet.

Scavenging is not turned on and we've got lots of stale/duplicate IP
records. We've been hesitant to activate scavenging because we are worried
about possible pitfalls.

One such problem I've read about is the refresh and no-refresh intervals
being too short. What would be a good setting?

What about statically assigned IPs, such as those belonging to servers?
Would they get scavenged too?

Any other conceivable problems we haven't thought of?
Click to expand...

Just don't set your scavening to SHORT intervals. Leave it LONGER
than DHCP leases AND longer than any two DCs will ever be out
of communication (e.g., longer than any possible WAN outage.)

People set scavening to hours or a few days, then have a WAN outage
and the DC records get scavenged so they can no longer replicate when
the WAN is restored.

The default minimum is 2+ weeks -- advice: Don't shorten it.
 
Back
Top