I have problems with my Secondary DNS server, all setup in Windows 2003/2008 environment.
Here is how it is setup (Workgroup conectivity, no AD):
- on 2 Windows 2003 machines I have 2 MS DNS servers installed. 1st is primary DNS, 2nd is secondary DNS, and it has only 1 NIC and 1 public IP
- on distant location I have 3rd Windows 2008 machine, which is Tertiary DNS. This machine has 3 NIC adapters and multiple public IP's
Now, DNS zones are configured with LIMITED zone transfer permissions, where zone transfers are only allowed to servers, listed in NS servers list. Which means, primary DNS zones can only be transfered to Secondary and Tetriary DNS server.
While transfer to 2nd server is NOT problematic (it has only 1 NIC and 1 IP), there are random problems with zone transfers to 3rd server (with multiple NIC's and IP's).
Because 3rd server sends zone update request on RANDOM public IP, despite of the fact, that DNS server is bind to separate NIC with only SINGLE IP. It actually does serve CLIENTS only on this dedicated IP, but zone update requests are sent out to Primary DNS on random public IP (one of all IP's this machine has).
Does anybody have an idea how to specify the outgoing IP for DNS zone update requests?