This is normal, but a bit cumbersome to explain. Let me try briefly. DHCP
lease duration: 2days. DNS Scavenging: 7days. ComputerA (say a Laptop) wakes
up on Monday and requestes an IP. DHCP gives it 1.1.1.1, and registers this
in DNS as an A record( ComputerA 1.1.1.1). ComputerA's user goes on a 3-day
vacation and takes his laptop with him. ComputerB user comes in on Thursday
and requests an IP. DHCP server has now put 1.1.1.1 in its pool of available
IPs (because it's over 2 days and ComputerA has not requested a renewal). So
ComputerB now gets 1.1.1.1 and this gets registered in DNS (ComputerB
1.1.1.1). This is NOT a duplicate. It's a different record altogether. And
remember, DNS has NOT cleaned up the old record (ComputerA 1.1.1.1) YET
because it's NOT more than 7 days old (scavenging length).
I hope that does not confuse you too terrinly. Now, what do we do with the
info? Follow this thread here:
http://www.mail-archive.com/activedi.../msg11017.html
and read more about Scavenging here:
http://www.microsoft.com/technet/pro...Scavenging.asp
--
Sincerely,
Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
"Herb Martin" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Are these dynamically registered? (Or manual?)
>
> Same name, different IPs?
>
> Consider using AD Integrated DNS but this shouldn't be happening
> anyway.
>
> --
> Herb Martin
> "Greg Haslett" <(E-Mail Removed)> wrote in message
> news:uw6b$(E-Mail Removed)...
> > Hi
> > I am new to microsoft DNS/DHCP implimentations.
> > We have win2k servers for DNS DHCP.
> > What is happening is duplicate entries in the DNS database. (two
different
> A
> > records for the same IP address) The scavenge time is set to 7 days and
> the
> > DHCP lease time is set to 2 days.
> > I have tried to perform a scavange stale resoure records but it did not
> > remove the duplicate entries.
> > any ideas ???
> >
> >
>
>