Letra ChicaHybrid DNS (on-premises ↔ cloud)
Each cloud's managed service for on-premises to resolve private cloud names and the other way around. All three solve the same problem; what changes is the cost model and who takes care of high availability.
Azure · Cheapest that meets it
AWS · Cheapest that meets it
GCP · Cheapest that meets it
| Option | On-premises resolves private cloud names | The cloud forwards domains to on-premises DNS | No fixed cost per endpoint | Cross-zone high availability without configuring it | Monthly floor |
|---|---|---|---|---|---|
| AzureAzure DNS Private Resolver | Meets | Meets | Doesn’t meetEach endpoint (inbound and outbound) and each ruleset is billed. | MeetsAutomatically zone-redundant in regions with zones, at no extra cost. | USD 363/ mo |
| AWSRoute 53 Resolver endpoints | Meets | Meets | Doesn’t meetHourly per IP (ENI); each endpoint needs at least 2. | With caveatsYou pick the subnet of each IP; AWS recommends different AZs. | USD 365/ mo |
| GCPCloud DNS (server policy de inbound + zona de forwarding) | Meets | Meets | MeetsThe server policy has no charge; you pay for zones (monthly) and queries. | With caveatsThere's one entry point (regional internal IP) per subnet. For HA, on-premises has to point at more than one. | USD 0.20/ mo |
Floors at list price as of 2026-10-06 (eastus · us-east-1 · us-east1), in USD, with no discounts or taxes.
Sources
Azure · Azure DNS Private Resolver
↗ learn.microsoft.com↗ learn.microsoft.com↗ azure.microsoft.com$ DNS Private Resolver — inbound endpoint × 1$ DNS Private Resolver — outbound endpoint × 1$ DNS Private Resolver — forwarding ruleset × 1
AWS · Route 53 Resolver endpoints
↗ docs.aws.amazon.com↗ docs.aws.amazon.com↗ aws.amazon.com$ Route 53 Resolver — endpoint IP (ENI) × 4
GCP · Cloud DNS (server policy de inbound + zona de forwarding)
↗ docs.cloud.google.com↗ docs.cloud.google.com↗ cloud.google.com$ Cloud DNS managed zone (private or forwarding) × 1
Verified on 2026-10-06 · Dictionary