DNS
最大8ホストへのラウンドロビン。ヘルスチェックはなく、死んだホストも取り分を保ちます。
このページはまだ日本語に翻訳されていません。
DNS answers one domain with several addresses, as a managed name service such as Route 53 does.
When to place it#
Place it when one App Server is not enough and you cannot yet afford a Load Balancer. The symptom is a board that refuses a second link from Users.
How it works#
It turns the one link from Users into many, giving each link an equal share of the traffic, which is round robin. Every request kind passes through unchanged, at no added latency and with no capacity limit. See DNS round robin.
DNS ignores size, so a small App Server gets the same share as a large one. It also has no health checks, so a dead host keeps its share and those requests fail.
Options#
| 設定項目 | 設定値 | 表示条件 |
|---|---|---|
| TTL | 30 s / 5 min / 1 h | ヘルスチェックの後 |
TTL: how long a resolver keeps an answer. The Health checks Research makes DNS drop a dead host once its TTL runs out, and lets you set the TTL. A short TTL drops a dead host faster and adds lookups. A long TTL keeps sending users to a host that died.
How it fails#
Instance failure: a host goes down, and its share of requests fails until DNS drops it, or never without Health checks.
Mixed sizes overload the smallest host first, because each gets an equal share. Keep hosts the same size.
Region outage#
Signs: One region's board goes grey and the DNS in it goes down.
Do now: Press Fail over on the banner. It needs Multiple zones and a second open region, and starts the Node again in the nearest other region, cold, for the price of a replacement. Otherwise it comes back when the incident ends: 180 sim seconds in the catalog, 60 once the error budget counts.
Prevent: Research Multiple regions, keep a copy in a second region, and add GeoDNS to send users there.
Tips#
Keep every host behind DNS the same size.
Replace DNS with a Load Balancer when you research Load balancing.
ルール#
- 追加のコピーは 1 つ前より 25% 高くなります。
- 売却すると、最後のコピーの価格の 50% が戻ります。
- サイズは 1 つだけです。