|
|
I am having a problem with controlling the DNS registration on a pair of
multi-homed clients. Here is the situation.
In one of our child domains, there are two DCs, both running 2003, but soon
to be upgraded to 2008. Two new member servers have been joined to the
domain, each with 4 NICs. 3 of these NICs are for Extranet clients and
should not be registered in DNS; I have configured these in the Properties
sheets, and that is working fine. The problem is with the 4th NIC. It is
multihomed, configured with 2 IP addresses; one needs to be registered in DNS
and the other should not, as it is a NAT'ed address. If I configure the NIC
to not register in DNS, within 24 hours, both IP addresses are scavenged from
the DNS server, and the operations people can't connect. If I configure them
to register in DNS, both IPs get registered, and every second attempt to
connect fails, since it resolves to the NAT'ed address. Is there a way to
ensure that one IP address stays registered in DNS, while a second IP on the
same adapter does not register?
Thanks,
|
|
One additional note:
The two new clients are running Windows Server 2008. The same configuration
works on several other servers, running Windows Server 2003. Apparently, in
Server 2003, only the first address on a NIC is registered in DNS, while in
2008, if a NIC is set to register in DNS, all IP adresses on that NIC are
registered. I am hoping there is a registry hack to cause the 2008 DNS
client to function like the 2003 client.
Thanks again.
|
|
|