> ## Documentation Index > Fetch the complete documentation index at: https://docs.tensor9.com/llms.txt > Use this file to discover all available pages before exploring further. # Cloud DNS > Cloud DNS APIs with Cloud Adapter. 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 | Environment | Mapping | | ----------- | ------- | | AWS | API | | Azure | API | 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 | Capability | Cloud DNS | AWS | Azure | | ------------ | --------- | ---- | ----- | | API coverage | full | high | high | ## On AWS ### Route53 | Operation | Area | Support | Depth | Notes | | ------------------------------------------ | ------- | ------------ | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------ | | Routing policies | Records | Out of scope | Most usage | Records with weighted, geographic or failover routing are flagged at build time. Those target features are not configured by this mapping. | | resourceRecordSets.create / patch / delete | Records | Supported | Common | record sets keep their name, type, time to live and data | | DNSSEC | Zones | Out of scope | Full surface | Signed zones are flagged at build time. The target supports DNSSEC, but this mapping does not configure it. | | Private zones | Zones | Out of scope | Most usage | Private zones are flagged at build time. This mapping does not create private hosted zones or silently publish them publicly. | | Response policies | Zones | Out of scope | Full surface | Response policies are flagged at build time. The target provides a resolver firewall, but this mapping does not configure it. | | managedZones.create / delete | Zones | Supported | Common | a public managed zone becomes a hosted zone on the target | 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 | Operation | Area | Support | Depth | Notes | | ------------------------------------------ | ------- | ------------ | ---------- | -------------------------------------------------------------------------------------------------------------------------------- | | Apex alias records | Records | Partial | Most usage | Azure aliases refer to Azure resources. An apex alias pointing elsewhere is rewritten, and the build identifies the result. | | Routing policies | Records | Out of scope | Most usage | Routing uses a separate target service, so records with weighted, geographic or failover policies are flagged at build time. | | resourceRecordSets.create / patch / delete | Records | Supported | Common | record sets keep their name, type, time to live and data | | Private zones | Zones | Out of scope | Most usage | Private zones are flagged at build time. This mapping does not create the target's private-zone resource or publish it publicly. | | managedZones.create / delete | Zones | Supported | Common | a public managed zone becomes a DNS zone on the target | 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](/cloud-adapter/getting-started/overview) and [configuration](/cloud-adapter/configuration/overview). Use [tuning](/cloud-adapter/tuning/overview) to understand supported request tags, [debugging](/cloud-adapter/debugging/overview) to investigate a request, and [High Fidelity Cloud Emulators](/cloud-adapter/local-testing/overview) to validate a bounded reproduction.