Cloud DNS
Capabilities
- GeoDNSThe DNS answer can depend on where the resolver is.
- DNS failoverDNS should stop handing out dead endpoints.
- DNSSECSigned answers belong in production DNS, not a lab zone.
- Anycast DNSAuthoritative DNS should not have a home region.
- DNS load balancingLoad balancing can start before the TCP handshake.
- DNS health checksConnect endpoint health to the record resolvers receive.
- multi-region DNSA multi-region app still starts with a DNS answer.
- low TTL DNSA 300-second TTL is a five-minute outage you already agreed to.
- CNAME flatteningThe apex should be allowed to point at a hostname.
- IPv6 DNSIPv6 is a DNS record and a DNS transport.
- vanity nameserversThe nameserver name can be yours. The network should not have to be.
- DNS traffic steeringRouting policy belongs in DNS, not only in the load balancer.
Cloud DNS
Workloads
- DNS for websitesWebsite DNS is the first hop of every page view.
- DNS for SaaSSaaS DNS is a product surface, not a registrar default.
- DNS for ecommerceA store that cannot resolve cannot check out.
- DNS for APIsClients cache API answers. Make those answers deliberate.
- DNS for WordPressWordPress migrations fail on DNS more often than on plugins.
Also on this network
Cloud CDN and Cloud DNS share 210+ locations. Delivery and authoritative routing are separate products with their own landing pages.
Browse CDN use cases