Amazon Route 53 Hosted Zone
Does ZopNight manage Amazon Route 53 Hosted Zone?
Route 53 hosted zones bill a flat monthly fee per zone plus per-query charges as traffic resolves records. Zones for retired domains and duplicated test zones keep charging indefinitely. ZopNight discovers every hosted zone on its 6-hour inventory pass, attributes DNS spend from Cost Explorer or CUR 2.0, and flags unused zones.
Rules that fire on Amazon Route 53 Hosted Zone
No active rule family targets Amazon Route 53 Hosted Zone today. Rules that used to are retired, and retired rules publish no pages and fire no findings. Scheduling and permissions coverage are unaffected.
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery, cost tracking, and recommendations only. |
A Route 53 hosted zone holds the DNS records for a domain, billed per zone per month plus query volume. Zones for retired domains and duplicated test zones add up quietly across large accounts.
Zone fees and query volume
Route 53’s meter splits in two: a fixed monthly fee for each hosted zone, and per-query charges that scale with resolution traffic against its records. Queries against alias records pointing at AWS resources resolve free, which is why most zones’ spend is dominated by the flat fee rather than traffic. The fee is trivially small per zone and completely insensitive to whether the domain still matters. A zone for a product retired two years ago bills the same as the production apex.
ZopNight and the DNS estate
Hosted zones are discovered via a dedicated provider on the 6-hour cycle, and DNS spend is attributed per zone from Cost Explorer or CUR 2.0. Hygiene recommendations focus on unused zones: private zones attached to VPCs that no longer exist, zones whose records all point at decommissioned infrastructure, and duplicate zones for the same name created during migrations. DNS has no concept of stopping, so the output is inventory clarity and a cleanup list, not scheduling.
Why dead zones accumulate
Domains lapse but their zones persist, because deleting a registrar entry and deleting the hosted zone are separate acts owned by different people. Test zones multiply, because engineers create a zone per experiment and the flat fee makes each one look ignorable. And acquisitions bring whole zone portfolios along, where nobody on the receiving team can vouch for which names are still referenced by customers or certificates.
Walking the hosted zones list
The Route 53 console’s Hosted zones view lists every zone with its record count and whether it is public or private. Query metrics per zone (via CloudWatch) separate the living from the dead: a public zone with zero queries over a quarter, or a private zone with no associated VPC, is a deletion candidate, once you have checked for lingering NS delegations and ACM validation records.