Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Can I get some advice on where to look for setting up my web server A so that if I have to bring it down for maintenance, all web traffic will go to my backup server B. I thought about changing DNS entry but that will take time to update.
Here are some options, each with their advantages and drawbacks.
- DNS updates can be scripted with the nsupdate command, but yeah, depending on the TTL of the A record, it can take a while to propagate. You could resolve that by issuing the nsupdate command, giving it some time to propagate, and then shutting down server A.
- If what you're looking for is instantaneous failover, you could look into a load balancer. There are software solutions for that, but they end up facing the same problem... you end up doing maintenance on the load balancing server. It's usually done by setting up another apache server as an http proxy.
- Big business tends to use an appliance for this function. They're not cheap.
Here are some options, each with their advantages and drawbacks.
- DNS updates can be scripted with the nsupdate command, but yeah, depending on the TTL of the A record, it can take a while to propagate. You could resolve that by issuing the nsupdate command, giving it some time to propagate, and then shutting down server A.
- If what you're looking for is instantaneous failover, you could look into a load balancer. There are software solutions for that, but they end up facing the same problem... you end up doing maintenance on the load balancing server. It's usually done by setting up another apache server as an http proxy.
- Big business tends to use an appliance for this function. They're not cheap.
Thanks for your input. I think I'm goign to try duplicate IP for one domain name. Then disable round robin. And lower the TTL to 1/2 hour.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.