Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I am looking for DNS hosting that can detect my web server failure and switch to another A record automatically. Also, they should support baisc DNS admin stuff. My domain is currently hosted on name.com. Thanks.

share|improve this question

closed as not constructive by splattne Jan 22 '12 at 8:22

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

1  
There are a number of questions here about using DNS for failover. It might be worthwhile for you to have a read of some of the answers and comments. The general consensus is that it's not really a good idea. –  John Gardeniers Jan 20 '11 at 9:48
add comment

2 Answers 2

While I'm sure there are some services out there that might do this there is a big issue with doing this.

Scenario

Your primary server goes down. The dns tool sees that and switches the A record to the standby server.

Issue

Some clients have a cache on your hostname and don't see the change till their dns server clears the cache. Now if the service does a low ttl their dns server might not honor that if the ttl is too low.

Bigger Issue

Your primary server's uplink has a hiccup and you lose connection for 10 minutes. DNS service switches to new A record. Now some clients are hitting the secondary and some still trying to hit the primary.. Primary uplink is backup and you have clients hitting 2 server's

Might not be a big deal if everything is static content.. but can be a giant issue if you run a more dynamic site.

share|improve this answer
    
I haven't running a big site and am thinking that as a way for redundancy. Then I do not need to test it anymore. Thanks. –  fossilet Jan 20 '11 at 14:08
    
Couldn't the second issue be worked around by using a very low TTL paired with a DNS resolving the IP for the database server? In other words using something like sql.mydomain.com in your connection string. Then it does not matter if the user hits the secondary or primary web server. Both are using the same database. –  Adrian Grigore May 29 '11 at 8:49
add comment

Just use a load balancer, it does not matter on what platform, Win or Nix. If the code that is running on your web server does not need sessions to be persistent or you have some strange app the you can use round robin dns. ex: A web1.foo.bar = 1.2.3.4 A web2.foo.bar = 1.2.3.5 cname www = web1.foo.bar web2.foo.bar

so when you try to resolve www.foo.bar it will serve one of the 2 A records

HTH

share|improve this answer
    
But doesn' that create a single point of failure on the load balancer? –  Adrian Grigore May 29 '11 at 8:49
add comment

Not the answer you're looking for? Browse other questions tagged or ask your own question.