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 Azure 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
Azure DNS zones become Route 53 hosted zones. Record names, types, time to live and data are preserved. An alias to an Azure resource is retargeted to the resource produced by the build.
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
For private zones, the build creates records for the VMs it knows about. Route 53 does not automatically register a VM that later joins the network, so the build requires acknowledgement of that limitation.On Google Cloud
Cloud DNS
Azure DNS zones become Cloud DNS managed zones, preserving record names, types, time to live and data. An alias to an Azure resource is replaced with a record for the address of its target resource. Records that depend on health checks use Cloud DNS routing policies.