DHCP / DNS / scavenging

Hello,

I tried to understand how they work together...

On my DHCP server, I leave the default properties for the DHCP lease
duration (8 days). On my DNS server, I leave the default properties
for the zone Aging/Scavenging (no-refresh-interval and refresh
interval to 7 days).

If a computer "A" receive an IP on the 23/12/08 and this computer is
powered-off for 2 weeks, then another computer can receive the same IP
after 8 days. It means, I will have two computer's name pointing to
the same IP after 8 days? After 15 days the scavenging operation will
delete the DNS entry for computer "A"

Does it work this way ?

Thank you.

Chris



.

Relevant Pages

  • Re: Domain authentication problem
    ... configuration of Dynamic DNS, hence updates now enabled. ... restarting DHCP server restores this as default after I ... modern Windows versions where clients can register their own IP ...
    (microsoft.public.windows.server.networking)
  • Re: Constant "Acquiring Network Address" status; No IP address fro
    ... Look at the DHCP server event log for more info on this error" ... Nothing in the logs show ... "Mathieu CHATEAU" wrote: ... DNS update may file if there is a dns ownership issue. ...
    (microsoft.public.windows.server.networking)
  • Re: Networking between Irix and Osx
    ... Is your router a DHCP server? ... My router is a DHCP server and my G5 was already configured to ... keep networking information (ip, dns,etc.) from it. ... In the panel Modify Network Settings on Iris, i also try to write the ...
    (comp.sys.sgi.admin)
  • Re: Multiple PTR records wont go away in the reverse zone.
    ... What about the DHCP setting "Dynamically update DNS A and PTR records only ... if requested", so clients will specify. ... I do agree with all your DHCP server recommendations (especially entering ... there is no other reason for a client to register in DNS when off ...
    (microsoft.public.windows.server.dns)
  • Re: Update 2003 DNS with non-domain member clients
    ... I noticed there wasn't a subnet created in AD where the non-domain members PC ... Where SHOULD I see the update if the client isn't part of ... I have the DHCP handing out the DNS suffix to non-domain members ... Changed my DHCP server to 'Always dynamically update DNS A and PTR ...
    (microsoft.public.windows.server.dns)