AWS Route 53 Pricing Guide: Hosted Zones, DNS Queries, Health Checks

Route 53-style costs are typically a combination of hosted zone fees plus DNS query charges and (optionally) health checks. The best cost model starts with measured query volume.

What to model (the 3 line items)

• Hosted zones: how many zones you maintain across environments/accounts
• Standard queries/month: your actual DNS query volume
• Health checks: if you use DNS-level health checks or endpoint monitoring

How to get the inputs (without guessing)

• Zones: list public and private zones separately. In multi-account setups, zones often get duplicated across environments.
• Queries: prefer a measured window from query logs. If you do not have logs, start from DNS QPS/RPS and convert to monthly.
• Health checks: count them, and confirm whether you have per-endpoint checks, multi-region checks, or checks per record.

A fast estimate (2 scenarios, not 1)

Use AWS Route 53 Cost Calculator for a simple zones + queries + health checks model. Then refine query volume using metrics/logs from a representative time window.

• Baseline scenario: a typical week (exclude outage windows and launch days).
• Peak scenario: incident retry storms, cache misses, or a short-lived traffic spike. This is what prevents a budget from failing in real life.

Query estimation methods

Method A: From query logs (best)

• Enable Route 53 query logging and sample at least 7 days.
• Compute: queries/day by hosted zone and top record names.
• Use the peak day as a sanity check for incident windows.

Fast DNS cost formula

• Total monthly Route 53 cost = hosted zone fees + DNS query charges + health checks.
• DNS query charges = queries/month x effective query unit rate.
• Peak protection: budget with both baseline and incident retry scenarios.

Method B: From request rate (good first pass)

• Convert RPS/QPS to monthly queries using RPS to monthly requests.
• Apply a multiplier for retries and cache misses (use a separate peak scenario rather than one inflated average).

What usually causes surprise bills (and how to prevent them)

• Very low TTLs: every resolver cache refresh becomes a paid query. Low TTLs have a purpose, but treat them as a cost decision.
• Service scale-out: more pods/instances often means more DNS lookups (especially with chatty clients or short DNS caches in runtimes).
• Retry storms: outages can multiply DNS queries as clients retry or fail over. Keep a peak scenario in your model.
• Health check sprawl: checks per endpoint and per environment add steady monthly cost and can be missed in budgets.
• CNAME chains: not always a cost problem, but they can increase lookup behavior and worsen incident sensitivity.

Worked estimate template (copy/paste)

• Hosted zones cost = public zones + private zones (as applicable)
• Query cost = standard queries/month (baseline) + standard queries/month (peak scenario)
• Health checks cost = health checks/month (baseline) + any extra checks used only for peak events

How to validate the estimate

• In Cost Explorer / CUR, confirm you see distinct line items for hosted zones, queries, and health checks.
• Compare baseline vs peak: if peak is not materially higher, you may be missing incident behavior in your model.
• Audit the top record names from query logs and look for noisy internal service discovery patterns.

TTL and query-volume decision guide

• Need fast failover: lower TTL only for critical records; keep default TTL higher elsewhere.
• Stable services: raise TTL to reduce resolver refresh frequency and query cost.
• Frequent deploys: use staged TTL changes during rollout windows, then restore normal values.
• Incident response: capture retry multipliers and include them in the peak scenario.

Failure patterns

• Applying one low TTL policy to every record type.
• Using traffic RPS as DNS query volume without resolver behavior checks.
• Ignoring health-check sprawl across environments.
• Estimating only baseline and skipping retry-storm budgets.

Related tools

Sources

• Amazon Route 53 pricing
• Route 53 query logging

Related guides

Related calculators

FAQ