Submit an article about your scariest tech experience—and the solution—and you’ll be automatically entered to win one of 4 fantastic tech gadgets.
Solved
IP Failover For Internally Hosted Website
Posted on 2012-12-28
One of my clients hosts his own web server with a primary and a failover internet connection:
Lets say our primary IP is 1.1.1.1 and our backup is 2.2.2.2. GoDaddy hosts our name servers so anytime someone wants to go to www.ourdomain.com a DNS host also known as an A record is setup pointing to 1.1.1.1. This works well enough and people land on our website. However if our internet goes down the IP currently changes to 2.2.2.2 which will break the A record setup on GoDaddy and www.ourdomain.com will not resolve. The quick fix is to modify the A record on Godaddy to the failover IP. This will get the site back up and running in just a few minutes. This is the short term solution.
Given that DNS does not support IP failover here is the solution I propose. Assign the site the IP 3.3.3.3. This site is a service that monitors 1.1.1.1 and 2.2.2.2. By default it will forward all traffic to 1.1.1.1 however if the site goes down it will automatically failover to 2.2.2.2.
What solutions do you suggest for this type of issue? Currently they are happy hosting on site they just need a way for the IP to failover
Lets say our primary IP is 1.1.1.1 and our backup is 2.2.2.2. GoDaddy hosts our name servers so anytime someone wants to go to www.ourdomain.com a DNS host also known as an A record is setup pointing to 1.1.1.1. This works well enough and people land on our website. However if our internet goes down the IP currently changes to 2.2.2.2 which will break the A record setup on GoDaddy and www.ourdomain.com will not resolve. The quick fix is to modify the A record on Godaddy to the failover IP. This will get the site back up and running in just a few minutes. This is the short term solution.
Given that DNS does not support IP failover here is the solution I propose. Assign the site the IP 3.3.3.3. This site is a service that monitors 1.1.1.1 and 2.2.2.2. By default it will forward all traffic to 1.1.1.1 however if the site goes down it will automatically failover to 2.2.2.2.
What solutions do you suggest for this type of issue? Currently they are happy hosting on site they just need a way for the IP to failover
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2
2
7 Comments
Active today
Are the two Internet connections always up?
You could use dynamic DNS updates to maintain the record for www pointing to both IPS, load balancing the traffic, when one connection goes away so s the matching record.
If you use the ISP connection in active/failover mode I.e. the routing table is weighted.
Your monitoring process could use dynamic updates to register the host based on the IP from which the request is being made.
The failover period will depend on your TTL setting on the record.
I.e. 30 seconds will mean that the transition of visitors between the two IPs will be 30 seconds between access attempts.
You could delegate the www.ourdomain.com from godaddy to your cloud based DNS if available that will be updated based on the site.
I.e. www.ourdomain.com. IN NS IP1.ourdomain.com.
www.ourdomain.com. IN NS IP2.ourdomain.com.
Each one will fall or stand with the provider. I.e. 1.1.1.1 goes down, all DNS lookups will go to 2.2.2.2 which will reference itself.
When both are on, the request will be distributed between the two IPs.
You could use dynamic DNS updates to maintain the record for www pointing to both IPS, load balancing the traffic, when one connection goes away so s the matching record.
If you use the ISP connection in active/failover mode I.e. the routing table is weighted.
Your monitoring process could use dynamic updates to register the host based on the IP from which the request is being made.
The failover period will depend on your TTL setting on the record.
I.e. 30 seconds will mean that the transition of visitors between the two IPs will be 30 seconds between access attempts.
You could delegate the www.ourdomain.com from godaddy to your cloud based DNS if available that will be updated based on the site.
I.e. www.ourdomain.com. IN NS IP1.ourdomain.com.
www.ourdomain.com. IN NS IP2.ourdomain.com.
Each one will fall or stand with the provider. I.e. 1.1.1.1 goes down, all DNS lookups will go to 2.2.2.2 which will reference itself.
When both are on, the request will be distributed between the two IPs.
Active today
I have the same type of network setup, where my server is either available via 1.1.1.1 or 2.2.2.2, but never both addresses at the same
time.I use DNS Made Easy and their DNS Failover and Service Monitoring. They monitor my servers and change the A records
automatically as necessary. They return to the original IP when service is restored. I have had the service for several years and it works great. You should probably just move the entire DNS zone off GoDaddy to DNS Made Easy to get this to go. It would be a lot simpler than trying to delegate specific records, and I don't know how you would even do that for domain.com
http://www.dnsmadeeasy.com/dns-services/
time.I use DNS Made Easy and their DNS Failover and Service Monitoring. They monitor my servers and change the A records
automatically as necessary. They return to the original IP when service is restored. I have had the service for several years and it works great. You should probably just move the entire DNS zone off GoDaddy to DNS Made Easy to get this to go. It would be a lot simpler than trying to delegate specific records, and I don't know how you would even do that for domain.com
http://www.dnsmadeeasy.com/dns-services/
Three options worth considering:
Round Robin DNS:
Create two A records for WWW. DNS servers will usually return these randomly meaning that web traffic will use both lines in normal usage. If one line is down, some users will continue to work reducing the downtime in simple ways
DNS failover records:
Many DNS/nameserver providers CAN provide failover DNS records which update automatically. They arent cheap though.
Dynamic DNS service:
Using a dynamic DNS service allows DNS records to be updated automatically by running a program on your server that reports its current IP to the DNS provider.
Round Robin DNS:
Create two A records for WWW. DNS servers will usually return these randomly meaning that web traffic will use both lines in normal usage. If one line is down, some users will continue to work reducing the downtime in simple ways
DNS failover records:
Many DNS/nameserver providers CAN provide failover DNS records which update automatically. They arent cheap though.
Dynamic DNS service:
Using a dynamic DNS service allows DNS records to be updated automatically by running a program on your server that reports its current IP to the DNS provider.
Active today
IMHO round robin DNS will not work because clients usually only try the first address returned. If they get the wrong address, and 50% of the clients will get the wrong address, they won't even check for a new address until the TTL expires, and even then they have a 50% change of getting the wrong address, and at least some browsers like IE cache DNS responses and require a restart.
DNS Made Easy seems pretty affordable. The failover DNS service costs $4.95 per host per year. Out the door you gave a solution for $35pr year, which is a lot cheaper than your second circuit.
DDNS could work if you can update your address like every 5 minutes.
DNS Made Easy seems pretty affordable. The failover DNS service costs $4.95 per host per year. Out the door you gave a solution for $35pr year, which is a lot cheaper than your second circuit.
DDNS could work if you can update your address like every 5 minutes.
Active today
Failover DNS would/should include dynamic updating/monitoring that will remove the downed IP with TTL of 300 seconds will mean that it will take five minutes following a failure hen a system is actively accessing the site to transition. Reducing the TTL will speed up the transition at the expense of more frequent lookups.
DNS requests alternate the data returned
One query could have the response as ip1, ip2. After the TTL expires, a new query might get the response as ip2, ip1.
DNS requests alternate the data returned
One query could have the response as ip1, ip2. After the TTL expires, a new query might get the response as ip2, ip1.
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Originally, this post was published on Monitis Blog, you can check it
here
.
It goes without saying that technology has transformed society and the very nature of how we live, work, and communicate in ways that would’ve been incomprehensible 5 ye…
- Web Development
- Networking
- Web Development Software
- Monitis
- IT Administration
- *Automation, *DevOps
Although a lot of people devote their energy toward marketing for specific industries, there are some basic principles that can be applied to any sector imaginable. We’ll look at four steps to take and examine how those steps were put into action fo…
This tutorial will teach you the core code needed to finalize the addition of a watermark to your image. The viewer will use a small PHP class to learn and create a watermark.
This Micro Tutorial will explain how to export DynamoDB tables in Amazon Web Services.
Suggested Courses
Course of the Month11 days, 4 hours left to enroll
618 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.