---
title: "Amazon Route 53 private hosted zones now support public DNS fallback — Cloud Changelog"
description: "Amazon Route 53 private hosted zones now support public DNS fallback. When a query for a name in your private hosted zone's domain doesn't match a record…"
url: "https://cloudchangelog.com/a/2026-11-route-53-public-dns-fallback"
updated: "2026-11-21"
---

[Back to feed](https://cloudchangelog.com/feed/2026-W47)

November 20, 2026 · AWS

# Amazon Route 53 private hosted zones now support public DNS fallback

- [Amazon Route 53](https://cloudchangelog.com/products/aws/route-53)
- [Networking and content delivery](https://cloudchangelog.com/search?q=networking)

Amazon Route 53 private hosted zones now support public DNS fallback. When a query for a name in your private hosted zone's domain doesn't match a record in the zone, Route 53 returns the answer from public DNS instead of a "name not found" (NXDOMAIN) error. Public DNS fallback is part of the [Advanced Hosted Zones](https://aws.amazon.com/about-aws/whats-new/2026/11/route-53-offers-advanced-hosted-zones/) offering.

Until now, Route 53 treated an associated private hosted zone as fully authoritative for its domain, so queries for names that weren't in the zone returned NXDOMAIN. To resolve a few names privately, customers also had to copy every other record from their public zone into the private hosted zone and keep the two in sync. With public DNS fallback, you add only the names you need privately, and every other name resolves from your existing public DNS. For example, your private hosted zone for example.com points example.com to a private endpoint, while partner.example.com exists only in public DNS. Before, a lookup for partner.example.com returned NXDOMAIN. Now it resolves from public DNS.

To get started, create a private Advanced Hosted Zone or upgrade an existing private hosted zone, and then turn on public DNS fallback. You can use the Route 53 console, API, AWS CLI, AWS SDKs, or AWS CloudFormation.

Public DNS fallback is available in all AWS commercial Regions where Route 53 private hosted zones are available. To learn more, see [Enabling public DNS fallback for a private hosted zone](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-public-dns-fallback.html) in the Route 53 Developer Guide and the [Route 53 pricing page](https://aws.amazon.com/route53/pricing/).

Get changes like this in your inbox

Your email address

Free, every Monday: what changed across AWS, Google Cloud, Azure, Cloudflare and the AI providers. We email you a link to confirm.

Free. Unsubscribe any time.

[Read on aws.amazon.com](https://aws.amazon.com/about-aws/whats-new/2026/11/route-53-public-dns-fallback/)

## Related updates

- Nov 20, 2026

  [Amazon Route 53 now offers Advanced Hosted Zones](https://cloudchangelog.com/a/2026-11-route-53-offers-advanced-hosted-zones)
- Nov 19, 2025

  [Amazon Route 53 DNS service now supports AWS PrivateLink](https://cloudchangelog.com/a/2025-11-amazon-route-53-dns-service-aws-privatelink)
- Nov 19, 2026

  [Amazon Route 53 now supports health checks for private endpoints](https://cloudchangelog.com/a/2026-11-route-53-private-endpoint-health-checks)
- Jul 15, 2026

  [Gateway, DNS - Internal DNS is now generally available](https://cloudchangelog.com/cloudflare/2026-07-15-internal-dns-ga) · Cloudflare
- Feb 10, 2025

  [Generally Available: Fallback to Internet on Private DNS Zones](https://cloudchangelog.com/azure/480005) · Azure

[All Amazon Route 53 changes](https://cloudchangelog.com/products/aws/route-53)

## Contact

- [YouTube](https://www.youtube.com/@cloudchangelog)
