Choose a DNS service by its change workflow, availability, access controls, and recovery behavior rather than by whether it was bundled with registration.

What registrar DNS is good at

Holding a zone while the site is not a product. A few records, high TTLs, mail at Google or Microsoft, no geo, no failover.

The delivery model

How it works

Registrar DNS vs Cloud DNS

  1. 01RequirementsDefine records, routing, DNSSEC, and access needs.
  2. 02EvaluateTest changes, monitoring, and failure behavior.
  3. 03MigrateReconcile the zone before changing delegation.
Conceptual model for this configuration. The actual path depends on provider policy and application behavior.

What production DNS has to do

Anycast authority, DDoS-protected nameservers, CNAME flattening for the apex, GeoDNS, weights, health checks and a TTL you can actually use. Cloud DNS is that control plane.

You can move DNS without moving the website

Import the zone, preserve MX, delegate NS, then later point the apex at Cloud CDN. They are separate cutovers.

SaaS onboarding is the giveaway

If you provision customer CNAMEs through an API, you are already a DNS product. Registrar panels do not scale to that.

Validate before production

Export the full zone and compare records, TTLs, and DNSSEC state on the new service. Include mail, verification, and delegated subzones. Keep the old authority serving consistent data while delegation caches converge.

  • Record the configuration and expected result before changing traffic.
  • Keep evidence of the test and a working rollback for the previous behavior.

Sources & further reading