On Wed, 2009-05-13 at 05:38 -0400, Picher, Michael wrote: > I don’t recall seeing this discussed so please excuse me if it has > been. > > > > During a HA install, the master server is typically installed and > setup as its own DNS server. > > > > Next when the distributed server gets installed, we also need this > server to be a DNS server for DNS failover (assuming the first server > goes away). > > > > So, during the distributed install, DNS is installed and I pointed the > first forwarder at the master server and the second forwarder off to > the internet. However, during the install the first DNS server added > to resolv.conf is 127.0.0.1 and the SIP domain zone is already on the > distributed server, there is no record yet of the Master server in the > zone file. The result is that the distributed server can not find the > master server. > > > > If I drop out of the install wizard, move 127.0.0.1 down one line in > resolv.conf, restart the network services and then restart the wizard > the distributed server install completes properly. > > > > Of course if separate DNS servers were being used this wouldn’t be an > issue, but I don’t know that we should assume that.
Good catch Michael. I think that the right fix is to put the IP address of the Master into resolv.conf as the second choice - in the bootstrap case the secondary will time out looking up on its local server (which is not initialized yet), and then use the Master to do the resolution. Please file an issue. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
