My network has 750 Windows XP laptops all with both an Ethernet and a wireless network adapter. On the server side we use standard Windows 2000 AD with Windows DHCP and DNS.
The problem is that each host gets two A records. For example, the wireless NIC for "host1.domain.com" might get assigned an IP which then results in an A record matching "host1.domain.com" to 10.100.10.50 while the Ethernet NIC gets and IP matching "host1.domain.com" to 10.100.10.60 for the Ethernet card.
This is problematic for two reasons. First, I have no control over which NIC I connect to when using the hostname "host1.domain.com". Of course, I could lookup the DHCP lease and determine which adapter is which by the hardware address, but this hardly convenient. Secondly, I have a need to be able to do a reverse lookup on an IP and know whether the IP was from a wireless or wired NIC. Currently a reverse lookup for either 10.100.10.50 or .60 would both yield "host1.domain.com".
What I'd like is to have the Ethernet NIC IP matched to an A record for "host1.domain.com" with the Wireless NIC IP matched to an A record for "host1.wifi.domain.com" or some solution similar to this which alters the hostname in the DNS record. Any suggestions for how to make this happen short of managing 1500 DHCP reservations which isn't an option?