Skip to content

Instantly share code, notes, and snippets.

@taisyo7333

taisyo7333/dns_failover_ttl.md

Last active July 15, 2017 00:25
Show Gist options
  • Save taisyo7333/d9ef9dfb1962d5ea8dd63fd722f9b9a3 to your computer and use it in GitHub Desktop.
Save taisyo7333/d9ef9dfb1962d5ea8dd63fd722f9b9a3 to your computer and use it in GitHub Desktop.
Download ZIP
DNS failoverについて
Raw
dns_failover_ttl.md

support.dnsmadeeasy

  • TTL を 180sec - 300sec に設定した方がよい。
  • 正しく設定しても最大で10min DNSの伝播に時間がかかるケースがある。
  • PC内にある名前解決キャッシュはTTLをベースに更新される

End clients who have queried for your IP address recently will have the IP cached in their local resolving name server held by their ISP. This cache time is based on the TTL of your record. Records that use DNS Failover should have a shorter TTL between 180 and 300 seconds to minimize this cache time. Worst case scenario it will be about 10 minutes before your new IP is propagated on cached systems if the TTL is set correctly.

https://support.dnsmadeeasy.com/index.php?/Knowledgebase/Article/View/71/12/how-does-the-ttl-of-a-record-affect-dns-failover

AWS

DNS フェイルオーバーを使用するときは、TTL を 60 秒以下にすることをお勧めします。これは、障害状態のエンドポイントへのトラフィックルーティングを停止するのに要する時間を最小化するためです。

https://aws.amazon.com/jp/route53/faqs/

Why is DNS failover not recommended?

https://serverfault.com/questions/60553/why-is-dns-failover-not-recommended

AWS の DNS フェイルオーバーで、サーバレス＆高可用性 Sorry ページを構築する

http://ceblog.mediba.jp/post/140328272267/aws-%E3%81%AE-dns-%E3%83%95%E3%82%A7%E3%82%A4%E3%83%AB%E3%82%AA%E3%83%BC%E3%83%90%E3%83%BC%E3%81%A7%E3%82%B5%E3%83%BC%E3%83%90%E3%83%AC%E3%82%B9%E9%AB%98%E5%8F%AF%E7%94%A8%E6%80%A7-sorry-%E3%83%9A%E3%83%BC%E3%82%B8%E3%82%92%E6%A7%8B%E7%AF%89%E3%81%99%E3%82%8B

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment