What I currently have is the following
EC2x2 Instance in Tokyo (1 Proxy 1 Application)
EC2x2 Instance in Singapore (1 Proxy 1 Application)

With another another provider we have geo dns, so Tokyo users go to Tokyo instance and Singapore to Singapore.

I'm looking at moving to Route53 (I already have other DNS zones with Amazon) because I'd like to take advantage of the failover with Health Check. Having looked at the examples of how to configure it, I'm still unsure how to configure what I want, which is as follows.

I've configured 2 health checks one for each location, and these are working.
I've configured 2 DNS entries both called proxy.domain.com each with a routing policy of GeoLocation and selected Japan and Singapore and add the relevant EC2 IP to each.
I'm now trying to configure the cname site.domain.com so that if either location is unavailable users will fail over to the other instance.

However what seems to happen is what I also expect to happen. Even when the DNS fails over because the secondary target is the same DNS name as the primary target, the location of the user always wins and the other instance IP is never returned. Example

Japan ip: Singapore ip:

From Singapore Ping site.domain.com >
Turn off Singapore (Health check confirms unhealthy)
Waiting for TTLs to expire, flushdns.
From Singapore Ping site.domain.com > (At this point I want this to return


What you would need to do is setup an alias tree, similar to How Health Checks Work in More Complex Amazon Route 53 Configurations, and ensuring evaluate target health is set to true.

proxy.domain.com / type geo | location: default -> alias -> wrr.domain.com

proxy.domain.com / type geo | location: Japan -> alias -> japan.domain.com

proxy.domain.com / type geo | location: Singapore -> alias -> sin.domain.com

wrr.domain.com / type wrr | weight 1 --> Japan.domain.com

wrr.domain.com / type wrr | weight 1 --> sin.domain.com

Sin.domain.com / type failover primary | associate with health check

Japan.domain.com / type failover primary | associate with health check

  • This seems to make perfect sense but I don't get the expected results. I did the above but I created a health check that I knew would fail and associated that with japan.domain.com and expected to get the IP for sin back but according to www.whatsmydns.net I get a selection of sin/jap about 50/50 even though the health check shows unhealthy and the other shows healthy – Drifter104 Jun 18 '15 at 9:45
  • I got this working by doing exactly what was on the link, which was slightly different to what is in the post. I decided that actually I want the fast response, and if the Japan one responds with a lower latency then the user shouldn't be penalised for being closer to Singapore. – Drifter104 Jun 18 '15 at 11:54

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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