Cloud DNS

This page describes how Cloud DNS maps to services in the environment where the application runs. Some profiles adapt origin API calls; others translate infrastructure or document target-native behavior.

​

Supported environments

API means the profile adapts origin API behavior. Infrastructure means the profile changes provisioned resources or documents a target-native alternative without promising an origin API endpoint. Check the operation and capability tables for the behavior your application depends on.

​

How the targets compare

Each row compares a capability of Cloud DNS with its adaptation on each target. A dash means this profile does not state the capability for that target.

​

Cloud Adapter

​

On AWS

​

Route53

A public Cloud DNS zone becomes a Route 53 hosted zone. Records preserve their name, type, time to live and data.

​

Zone updates and query traffic

The adapter manages the source zone and record operations through the target DNS API. Once applied, the target DNS service answers queries. Management completion and DNS caching are separate: clients can continue seeing an earlier answer until its time to live expires.

​

Delegation and cutover

Copy records and validate the target answers before changing a public domain’s delegation at its registrar or parent zone. Keep the old and new zones consistent during the transition. Test private names from the intended networks where private zones are supported; record contents alone do not establish visibility.

​

Compatibility differences

This mapping does not cover weighted, geographic or failover routing, private zones, zone signing or response policies. The build flags records with routing policies so those policies are not silently lost.

​

On Azure

​

Azure DNS

A public Cloud DNS zone becomes an Azure DNS zone. Record names, types, time to live and data are preserved.

​

Zone updates and query traffic

The adapter manages the source zone and record operations through the target DNS API. Once applied, the target DNS service answers queries. Management completion and DNS caching are separate: clients can continue seeing an earlier answer until its time to live expires.

​

Delegation and cutover

Copy records and validate the target answers before changing a public domain’s delegation at its registrar or parent zone. Keep the old and new zones consistent during the transition. Test private names from the intended networks where private zones are supported; record contents alone do not establish visibility.

​

Compatibility differences

Azure alias records refer to Azure resources. The build identifies the rewrite for an apex alias pointing outside Azure. Routing policies also require review: Azure handles traffic routing through a separate service, so the build flags records that use them.

​

Existing data and credentials

Selecting a backend does not copy existing data, credentials or access policies. Plan and verify migration separately before changing an application’s endpoint. Do not assume an identifier, credential or encrypted value from the origin service works unchanged on the target.

​

Configure, tune and debug

Start with setup and configuration. Use tuning to understand supported request tags, debugging to investigate a request, and High Fidelity Cloud Emulators to validate a bounded reproduction.