• Status: Solved
  • Priority: Medium
  • Security: Private
  • Views: 38
  • Last Modified:

INBOUND DNS failover with AWS Route 53

Hi everyone.

We currently use a self-hosted [in-house] Microsoft Lync solution for VOIP with 4 Microsoft servers. Meaning, we have this in-house on our KVM cluster.
External dns records are at our registrar, and resolve to wan rout able external ip addreses of which are further NAT's to the internal addresses via our Sonicwall using Comcast.

We are getting another ATT line, with 5 more rout-able IP addresses, and want to set up DNS fail over for INBOUND connections to the servers above, should one internet line go down. I know outbound is possible, we use it now, I'm talking about Inbound only.

My question is, does Amazon Route 53 support DNS failover, for a self-hosted connection, and not just for whats in the  VPC.

My alternative is to implement one of several hardware solutions which addres this issue.




2 Solutions
Of course it does.
You have to set up an A record or a CNAME pointing to your primary cluster, and ensure that ALL devices, PCs, servers use the FQDN and not directly the IP address. The ttl will be low, or failover will not really work.
You will have to setup health checks so R53 can check your clusters.

Having said that, there may be better alternatives than Route 53. Take ns1 for example (www.ns1.com). Configuration is easier, and they support routing and failover scenarios even when you cannot allow external inbound traffic to monitor your endpoints.
petersystems engineerAuthor Commented:
Thank you, I also verified this with AWS:

I have read through the case and understand you wish to know if Route 53 can perform fail-over health checks on resources that are not inside an VPC. The answer is yes. However, you will need to have your DNS hosted in Route 53 for the records using health checks to work. For example, consider "example.com" is your domain. Now, you need to create fail-over records, one primary and the other secondary. You will need to create example.com pointing to ISP1 line as primary and example.com pointing to ISP2 as secondary. To create these records, R53 must host the hosted zone for the domain example.com. The procedure for this can be found in document [1]. Document [2] is a guide on how to create DNS fail-over records. Please feel free to let us know if you require further clarification. I am unable to comment on the hardware alternatives as AWS premium support is not trained in infrastructure architecture. Resources: [1] https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-in-use.html [2] https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover.html Best regards, Nigel F. Amazon Web Services
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now