Mobile app version of vmapp.org
Login or Join
Mendez628

: Best compromise for low DNS TTL for failover, versus high TTL to reduce DNS lookup time We're looking at lowering our DNS A record TTL to around 1 minute, to enable us to quickly switch to

@Mendez628

Posted in: #Dns

We're looking at lowering our DNS A record TTL to around 1 minute, to enable us to quickly switch to a backup server should the main one fail (whether this is automatic, using AWS Health Checks etc, or manual, is largely irrelevant to this question).

I'm aware this will put a significantly higher load on the DNS server, but this isn't an issue.

What I'm concerned about it how the total site load time will be increased, because of the additional overhead of having to look up the DNS records with a lot more requests.

How to I balance these issues?

I'm obviously disregarding factors outside my control, such as ISP DNS caching.

10.01% popularity Vote Up Vote Down


Login to follow query

More posts by @Mendez628

1 Comments

Sorted by latest first Latest Oldest Best

 

@Sent6035632

You should instead have some kind of proxy (or load-balancer) in place which would route all the traffic to backup server when main server is down without requiring to do any DNS changes.

The implementation on this depends a lot on what you are trying to accomplish though, but the information in the question that you have provided is more general.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme