Re: Duplicate reverse lookup entries/nslookup problems
- From: "Todd J Heron [MVP]" <todd_heron(delete)@hotmail.com>
- Date: Fri, 13 Jan 2006 21:13:16 -0500
"Roger" <roger@xxxxxxxxxxx> wrote in message news:%23hRgKSKGGHA.3624@xxxxxxxxxxxxxxxxxxxxxxx
On my internal network, when using nslookup to resolve an ip to computer name, it sometimes resolves to an incorrect host name. I looked into the reverse lookup zone and found that there are duplicate entries for some ip addresses, and lots of old entries. What should I do to keep it accurate? I'm using dhcp to serve out addresses - I'm guessing that I need to change something on the dhcp server or client end of things.
Duplicate records may exist in DDNS due to DHCP not discarding A & PTR records. On the DHCP server, ensure "Discard A and PTR records when lease is deleted" is enabled under the DHCP server properties > DNS tab. However, this does not always clean everything up, as in instances where machines crash, are shutdown ungracefully, or say a laptop which is just disconnected. The IP is not released in any of these examples. A machine cannot update or delete a record when that record is created by another machine. The result is it creates another PTR record for the same IP address. The DHCP server also cannot update the record because it is not the owner. You need to enable scavenging to remove these records. There is a proactive approach which you can take via DHCP which Kevin Goodknecht often recommends. See link below.
http://groups.google.com/group/microsoft.public.windows.server.dns/browse_thread/thread/34d1fe4a15bb7f36/1536576a349fbc19?lnk=st&q=%22
-- Todd J Heron, MVP Windows Server - Networking MCSE - Windows Server 2003/2000/NT; CCA
.
- Follow-Ups:
- References:
- Prev by Date: Re: Newbie: 2DC's error 4004
- Next by Date: Re: Second DNS
- Previous by thread: Duplicate reverse lookup entries/nslookup problems
- Next by thread: Re: Duplicate reverse lookup entries/nslookup problems
- Index(es):
Relevant Pages
|
