I’ve migrated one of our Tiger servers to Leopard and am encountering and issue with its multihomed setup that we didn’t have previously in Tiger.
With 4 NICs, only one is set to an IP that resolves to a FQDN in our ADS name space. 2 others are non-ADS names, and the other is on a 192.168.X.X private net. The ads name is registered with ADS domain name servers, and I have PTR records for reverse lookups. After binding with the AD plugin, everything is fine… however, as I setup the other NICs, their IPs get put in in the ADS namespace. Now, when I run a dig command against the ADS name, I get all 4 IP addresses of the NICs, all A records, each associated with the one ADS name. As you can imagine, this makes calling any network service with the ADS name impossible, because it won’t resolve to one IP.
I spoke with our ADS admins and it is possible to specify which NIC will register itself with ADS, but it seems Apple’s plugin is registering them all. Any way around this?
Seems to be a new leopard thing… anyone else seen this?
.
.
Comments are closed