Duplicate reverse lookup entries/nslookup problems

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.


.

Relevant Pages

  • RE: Client IP/DHCP
    ... > DHCP server. ... > Let me know if this still does not resolve your problem. ... >> some folders in there labelled with random numbers and letters. ... >>> then type regedit once in the registry follow the path I gave you on the ...
    (microsoft.public.windows.server.sbs)
  • The "Mshome.Net" issue
    ... Problems are to with VPN access and the DHCP server. ... we get IPNATHLP errors 30013 in the Event Log about the DHCP allocator. ... Resolve Ip Addresses for checkbox under the Name Resolution tab. ...
    (microsoft.public.windows.server.sbs)
  • Re: dhcppc1 in the file /etc/hosts error
    ... den 09.01.2005 schrieb dmitrik@mindspring.com um 18:32: ... > any idea how to resolve this or actually add it into the file? ... "dhcppc1" is a host which gets his IP by a DHCP server? ... legal statement: http://www.uni-x.org/legal.html Fedora GNU/Linux Core 2 on Athlon kernel 2.6.9-1.6_FC2smp ...
    (Fedora)
  • Re: domain login issues
    ... DNS will try to resolve names internally first before reaching out to the ... network name to one that cannot resolve outside the network - that would ... > I will try moving the DHCP server to the server. ...
    (microsoft.public.win2000.networking)
  • DNS Problem?
    ... Windowx XP clients loose the ability to resolve machine names that have ... The DHCP Server service will not start on SBS 2003. ...
    (microsoft.public.backoffice.smallbiz)
Loading