Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Disaster Recovery: How does DNS failover work for AWS Disaster Recovery?

0

Hi re:Post,

I am not a network/domain admin but have some general questions regarding DR with an AWS framework.

Suppose the servers in our Ohio region go down.

We recreate all servers via snapshots in Oregon region.

How does the DNS load balancer 'know' about the new servers in Oregon region?

How does DNS failover work in this situation?

I've read this article: https://docs.aws.amazon.com/prescriptive-guidance/latest/strategy-database-disaster-recovery/defining.html

but I think it's just the tip of the iceberg so to speak, can you suggest other articles as well ?

Thank you for your time and help!

Best Regards,

Donald

Topics
StorageNetworking & Content Delivery
Tags
Disaster Recovery/Business ContinuityElastic Load BalancingAWS Elastic Disaster Recovery
Language
English

asked 2 years ago835 views

2 Answers
1
Accepted Answer

You will have a new load balancer in the new region.

Load balancers are regional.

You need to update the DNS records to point to the new load balancer.

Alternatively you could use global accelerator which points to your primary and secondary load balancer. This way you never need to update DNS. Failover would be built in

Another option is Route53 health check https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-failover.html

EXPERT

answered 2 years ago

EXPERT

reviewed 2 years ago

  • DC
    2 years ago

    Thank you Gary and Steve for your answers, link, and review of my questions! Best Regards, Donald

0

From https://arpio.io/failover-routing-for-disaster-recovery-ensuring-your-customers-get-to-the-good-place/

You have four options:

  1. A direct approach — manually update Route 53 DNS records. It’s effective but carries risks due to reliance on AWS control plane operations.
  2. Automatic failover with Route 53 health checks — it’s thorough but potentially indecisive. It removes manual intervention but requires precise health checks to avoid unnecessary failovers.
  3. Use Amazon Application Recovery Controller (ARC) — a sophisticated and resilient solution with a cost. ARC offers high availability and direct control over failover via data plane operations.
  4. Standby takes over primary (STOP) — pragmatic, cost-effective, and human-initiated without the risks of control plane reliance, making it a DIY version of ARC.

answered 2 years ago

  • DC
    2 years ago

    Hi Seth - thank you for you input and options ! We're looking at a possible hybrid approach utilizing options 3 and 4 at this time. Best Regards, Donald

  • Samantha Eliot
    2 years ago

    Hi Donald... glad my answer was helpful -- up-votes are always appreciated

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content