Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
well you've two stages here, knowing that something has failed and then separately taking action. Depending on how this is all built, this is often two fundamentally unrelated problems to deal with.
HA DNS is (surprisingly?) hard, things like DNS TTL's make failovers frequently slow for one thing. Can you define what sort of level of environment this is in? Is this a spare box in your mates kitchen, or a multi million dollar data centre?
Last edited by acid_kewpie; 06-28-2012 at 04:10 AM.
Thanks, our HO DNS is on the same network ..
HO and DRC site are connected with Leased-Line 100Mbps
HO DNS is on 172.16.0.31
and I want DRC DNS is on 172.16.0.131
OK, still far far too little information to really base much on...
your servers on are the same /24 subnet?? Or is this two /25s? This is internal traffic, so presumably this is more than a single IP fail over? What tools do you have at your disposal? are you just looking at adding open source software to any conveniently placed servers, or do you have $50,000 to buy a couple of F5 GTM devices? What ARE these DNS servers?
Hi, yes they are on the same subnet /22
and they are Bind Named Server that come with Centos 5.5
and I am looking for Open Source softwsre that can help me to do DNS failover
this doesn't cover a active / standby scenario though, and a third site from which they are monitoring might not suit your model. You could easily rework the logic though I'm sure.
Hmm... but then... Are you really after using DNS to provide the failover, or are you looking at the failover of the DNS servers themselves? If it IS the latter, which feels increasingly likely, then why do you need to do it at all? what's wrong with a standard master / slave scenario? What do you think will happen from a failover? If they are synchonrized, then just use them both all the time... no?
hmmm. . master and slave?? I never try it... can the slave able to do takeover when the master goes down?
do I need to also modify the slave when the master was modified or when new record added?
there is no "takeover", they both just work all the time, the slave being told of any updates by the master. You can also look at a dual master set up if you really want.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.