DNS & Traffic Management across clouds

Authoritative DNS zones and traffic steering (Cloud DNS, Edge DNS, Route management) as verified modules.

23 verified modules, 6 of them live-tested apply→verify→destroy; the rest are static-validated, live-test pending.

Compare by provider

ProviderModuleVerification
AkamaiAkamai Edge DNS Zone✓ live-tested
AkamaiAkamai GTM Failover/Weighted Domainstatic-validated
Alibaba CloudAn Alidns Zone with Its Records on the Default Line and the Nameservers Exportedstatic-validated
AWSDNS Firewall with Fail-Open Stated, Not Inheritedstatic-validated
AWSResolver Endpoints, Forwarding, Query Logs and DNSSECstatic-validated
AWSRoute 53 Hosted Zone & Records✓ live-tested
AzureA Private Resolver Whose Rules Forward and Whose VNets Are Linkedstatic-validated
AzureAzure Private DNS Zone✓ live-tested
AzureAzure Public DNS Zone & Records✓ live-tested
AzureAzure Traffic Manager Profile✓ live-tested
CivoA Civo DNS Zone with Its Records and the Nameservers for the Registrarstatic-validated
CloudflareCloudflare DNS & WAFstatic-validated
DigitalOceanA DNS Zone, and a Plain Account of Why It Is Not Yet Serving Anybodystatic-validated
ExoscaleAn Exoscale DNS Zone with Its Records and the Nameservers for the Registrarstatic-validated
Google CloudCloud DNS Zones & Records✓ live-tested
Huawei CloudA Huawei Cloud Public Zone with Record Sets, Signed, and the Nameservers Exportedstatic-validated
IBM CloudA Private Zone with the Permitted Networks Without Which It Resolves for Nobodystatic-validated
LinodeLinode DNS Zone & Recordsstatic-validated
Oracle CloudDNS Zone & Traffic Steeringstatic-validated
OVHcloudRecords and DNSSEC on an OVHcloud Zone You Already Havestatic-validated
ScalewayA Scaleway DNS Zone with Its Records and the Nameservers for the Registrarstatic-validated
Tencent CloudA DNSPod Zone with Its Records on the Default Line and the Nameservers Exportedstatic-validated
VultrA Vultr DNS Zone with Its Records, Signed, and the Nameservers for the Registrarstatic-validated

How to choose

Use the provider whose edge/anycast footprint matches your users; add traffic management (failover/GTM) only when you run multi-region.

When not to use

DNS is not a load balancer - failover via DNS is slow to converge because of resolver caching.

Other solutions