Yes I tried and it worked, but i need an easier way to do this. Kemal
On 9 June 2011 11:41, Michael Picher <[email protected]> wrote: > Kemal, > > Did you test what I suggested doing? > > Mike > > > 2011/6/9 Kemal Eroğlu <[email protected]> > >> Hello, >> >> First of all, in this case master is our DNS, but master also has an upper >> DNS which is the DNS we used in our company. >> >> I also think that something is wrong with the DNS resolving mechanism of >> the secondary machine. I used putty when the setup is working and it can >> ping the fqdn of primary server; but when it tries to connect the master in >> setup, it gives this error. I could not figure out why. >> >> I tried to add a new line to the /etc/hosts of secondary. It is working in >> this condition. But it is not a desired condition to apply this in every HA >> setup we do. >> >> I checked both server's /etc/resolv.conf files, they seemed OK to me. >> Secondary server's resolv.conf file is set by the setup script during the >> setup. So it has master IP address as its DNS. I think secondary server >> should query the master fqdn and the master should be able to resolve it >> normally. I found it strange. >> >> Best Regards, >> >> Kemal >> >> >> On 8 June 2011 22:32, Joe Micciche <[email protected]> wrote: >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> > Hello, >>> > I have an extended sipxecs 4.4 HA setup with one primary and one >>> redundant >>> > server. When I set up the redundant, during sipxecs-setup, in the last >>> step >>> > it asks for master-fqdn, master-ip and password to get the >>> configuration >>> > files from master. I provide the information but it gives an error, >>> "Failure >>> > fetching configuration from master .... Name or service not known.". It >>> > continuously gives this error, until I abort and redo the >>> "sipxecs-setup" >>> > from the beginning. I investigated about this and saw that, it somehow >>> > cannot resolve the fqdn of the master. Did you encounter such an error >>> or do >>> > you have any idea to fix this? >>> >>> I ran into this exact issue. Check /etc/resolv.conf on the redundant >>> server and make sure you have known good nameservers. Somehow my proxy >>> had a garbage entry in there which prevented it getting config from the >>> core sipxecs server - I removed the bad line and everything worked fine. >>> >>> - -- >>> ================================================================== >>> Joe Micciche [email protected] >>> Red Hat, Inc. http://www.redhat.com >>> Senior Communications Engineer X(81) 44554 >>> +1.919.754.4554 >>> ================================================================== >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.11 (GNU/Linux) >>> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ >>> >>> iEYEARECAAYFAk3vzlkACgkQJHjEUGX5D+GL1wCgxIstfwAA9GEitFmbi/Im3Hxa >>> qaoAnRcQFg1x4jAfBTnY2AMBjnc3eS9i >>> =mePE >>> -----END PGP SIGNATURE----- >>> _______________________________________________ >>> sipx-users mailing list >>> [email protected] >>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >>> >> >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > Michael Picher > eZuce > Director of Technical Services > O.978-296-1005 X2015 > M.207-956-0262 > @mpicher <http://twitter.com/mpicher> > www.ezuce.com > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
