I work in the desktop area and we see some peculiar things around DNS name resolution. When I ask our server guys, I get some answers that don't seem to make sense.
We are running Windows 2003 servers with Wins and my problems are:- 1. Duplicate IP entries in DNS. I have a program that gets a list of all workstations in Active Directory, then does a DNS lookup on them. I find multiple workstations with the same IP address. I assume that one of the machines is an old machine that no longer exists. If DHCP is so smart that it tells DNS when it assigns an address to a workstation, why doesn't it also tell DNS when it deassigns it? The lecturer at a course last week said we should "Turn on Scavenging" to delete the old ones. My server guys say they tried that, but it deleted all of the Static IP Addresses for printers. 2. Inconsistent responses with Reverse lookup. If my program does a reverse lookup on an IP address, sometimes I get a fully qualified name (presumably resolved in DNS) and sometimes just the nodename (presumably resolved in Wins). Now the latter would make sense if I had an IP Address that was defined in Wins but not in DHCP, but if I try and resolve the same IP address multiple times, sometimes I get the Full name, sometimes the short name. My Server guys tell me this is a feature of 2003. It sometimes tries Wins first, sometimes tries DNS first. Sounds a bit dodgey to me! Is it true and if so, is there a way to override this behaviour, ie direct the reverse lookup to:- - only use DNS - only use Wins - or only try Wins if DNS fails? Alan Cuthbertson List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
