Azure DNS costs

Tensor9 BYOC planning comparisons for azure::1.0.0::dns, with backend choices shown together. Read how Tensor9 estimates service-adapter costs for price scope and capacity qualification, or return to additional services.

​

Authoritative DNS zones and queries (Azure DNS) → Cloud DNS

Origin API: azure::1.0.0::dns. Target backend: google::1.0.0::dns. Designed mapping. This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend.

​

Authoritative DNS zones and queries (Azure DNS) · Authoritative DNS queries per second

Estimated monthly service charges by Authoritative DNS queries per second. Adapter hosting and Tensor9 fees are excluded. Source: eastus; target: us-central1; currency: USD. Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples. Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more. Curve assumptions

• Only this native meter varies; all other source usage and translation assumptions retain the displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
• Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. eastus → us-central1, USD/month.
• Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
• Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
• Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve’s workload note.
• Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
• Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
• Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
• Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
• A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
• This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
• Origin unit prices are cited provider list prices; capacity coefficients and translation assumptions are editable authored planning guesses, not measured capacity or a provider quote.
• Management requests do not reveal resource allocation or workload traffic. Provisioned resources and traffic are independent inputs.
• This compares authoritative zones and query meters; resolver forwarding has a different allocation and tariff.
• A cost scenario does not establish live-qualified runtime DNS propagation or public authority.
• Zone-months and authoritative queries are billed independently; management calls are free. Cloud DNS managed zones and regular queries; zone prices step down at 25 and 10,000 zones, query prices after one billion. Routing policy queries cost more. Cloud DNS bills no data transfer.
• Azure Retail Prices API: https://prices.azure.com/api/retail/prices
• Azure DNS pricing: https://azure.microsoft.com/en-us/pricing/details/dns/
• Cloud DNS pricing: https://cloud.google.com/dns/pricing

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:

• Health checks, DNSSEC premiums, resolver endpoints, query logs, domain registration and routing-policy premiums.
• Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
• Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: plan-3621287da74603b5d9b00a40473d7de0ccfc73db / 2026-10-22.planning.2. Curve: workload-1. Sources: Azure Retail Prices API, Azure DNS pricing, Cloud DNS pricing.

​

Authoritative DNS zones and queries (Azure DNS) → Route53

Origin API: azure::1.0.0::dns. Target backend: aws::1.0.0::route53. Designed mapping. This cost model describes an intended adapter. Its estimated price does not establish a delivered or selectable backend.

​

Authoritative DNS zones and queries (Azure DNS) · Authoritative DNS queries per second

Estimated monthly service charges by Authoritative DNS queries per second. Adapter hosting and Tensor9 fees are excluded. Source: eastus; target: us-east-1; currency: USD. Comparison pills describe all sampled scale points; card amounts show the named workload. Costs The Same means within 20% at every point. Costs Depend includes mixed results and unpriced samples. Exact sampled model outputs in USD/month. Difference means target minus origin; a positive difference means the target costs more. Curve assumptions

• Only this native meter varies; all other source usage and translation assumptions retain the displayed defaults. Editable authored planning guesses, not verified provider tariffs, benchmark measurements or a commercial quote. Other native meters retain their explicitly displayed default quantities.
• Planning estimate · editable authored rates and sizing assumptions dated 2026-10-22; not verified provider prices. eastus → us-east-1, USD/month.
• Source prices are reference charges, not an invoice. Target lines cover selected service usage/configuration only; adapter hosting and Tensor9 fees are excluded.
• Explicit tariff samples are not performance measurements or capacity qualification. No interpolation or break-even guarantee is implied.
• Variant assumptions show the first axis sample; any axis-dependent configuration is described by this curve’s workload note.
• Rates are cited provider list prices, editable for discounts, commitments or another region. Workload translation and capacity coefficients remain editable planning assumptions, not benchmark measurements or a commercial quote.
• Default-zero rates are explicit assumptions, not evidence that the deployed service or resource is free.
• Provisioned-unit minimums use an editable approximate allocation floor. Modeled target service cost is max(usage/allocation, minimum), with billable network, durable staging and dependent sinks added separately; actual RU/TU sizing, scaling increments and throughput remain unqualified.
• Durable staging is priced once: provisioned targets include adapter state in their selected allocation; native targets add a separate staging allocation when required. Adapter hosting is a separate allocation and must exclude resources already priced as staging, workers or target capacity.
• A declared adapter mapping and cost model do not establish implementation availability or service equivalence.
• This exact directed mapping has a design profile. Cost modeling does not establish an implemented or deployable adapter.
• Origin unit prices are cited provider list prices; capacity coefficients and translation assumptions are editable authored planning guesses, not measured capacity or a provider quote.
• Management requests do not reveal resource allocation or workload traffic. Provisioned resources and traffic are independent inputs.
• This compares authoritative zones and query meters; resolver forwarding has a different allocation and tariff.
• A cost scenario does not establish live-qualified runtime DNS propagation or public authority.
• Zone-months and authoritative queries are billed independently; management calls are free. Route 53 public hosted zones and standard queries; zone and query prices step down after 25 zones and one billion queries. Alias queries to AWS resources are free, and latency, geo and weighted routing queries cost more.
• Azure Retail Prices API: https://prices.azure.com/api/retail/prices
• Azure DNS pricing: https://azure.microsoft.com/en-us/pricing/details/dns/
• AWS Price List API: https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonRoute53/current/aws-other/index.json

Cost scope: Modeled target native service and explicitly modeled state allocation; hosting and Tensor9 fees only when supplied. Excluded costs and workload features:

• Health checks, DNSSEC premiums, resolver endpoints, query logs, domain registration and routing-policy premiums.
• Taxes, discounts, credits and free-tier allowances unless explicitly reflected in edited rates.
• Unmodeled dependent services, task execution and operations outside the selected workload family.

List prices read: 2026-10-22. Model: plan-685b86ede4026140c9329f1c1ba5160af2ff8c78 / 2026-10-22.planning.2. Curve: workload-1. Sources: Azure Retail Prices API, Azure DNS pricing, AWS Price List API. See the service catalog for operation coverage, supported directions and backend limitations.