Create the intended public zone through PD Google Cloud DNS, populate its records and then delegate the domain to its assigned nameservers. Creating DNS hosting is separate from registering the domain or moving its website and mailboxes.

Review the destination first

Confirm the provider connection and intended project. Search for an existing managed zone and check its DNS suffix before creating another copy. A missing-looking module result is not proof the provider has no zone; use the identity checks if necessary.

The connection’s target project comes from the saved service-account JSON. Confirm it before creating the zone; a provider label is not a project override.

Keep the source DNS records and previous service available during a move. Prepare website, mail, verification and any child-domain delegations before changing the registrar.

Create and populate

1. Open Google Cloud DNS → Zones and the intended provider.
2. Use the available create-zone action and enter the domain you intend to host.
3. Review the provider result and open the zone’s records.
4. Add the required ordinary records or use a reviewed import.
5. Verify the intended client binding and assigned nameserver set.

Google Cloud supplies the zone’s own apex NS and SOA records. Keep its authority information intact. This procedure is for ordinary public DNS hosting, not a private VPC or peering-zone configuration.

Delegate through the registrar

Set the domain’s nameservers at its registrar to the set assigned to this exact managed zone. Google’s nameserver guide explains that different managed zones can use different nameservers.

Keep the previous DNS answering through the resolver transition where applicable. Check authoritative records, then website, HTTPS and mail separately. Cached older answers can persist for their previous TTL even after the new provider is ready.

If the old zone is signed, plan the parent DS/signing transition using the DNSSEC scope guide. If creation times out, reconcile the actual existing zones before repeating it; do not assume an uncertain response means nothing was created.

See the PD Google Cloud DNS WHMCS guide for related tasks, or explore the module.