Create a public DNS zone through PD Azure DNS, populate its required records, then delegate the domain to that exact zone’s Azure nameservers. Zone creation is not domain registration and does not automatically move an existing website or mailbox.

Prepare the destination

Check the provider’s subscription/resource group and search for an existing zone before creating another. Confirm that the app can create DNS zones in the intended group and that the group already exists or its creation is separately authorised.

Keep the existing DNS service and a record export available during a move. Review website, mail, verification and subdomain requirements before changing nameservers.

Create and inspect

1. Open Azure DNS → Zones and choose the intended provider.
2. Use the available create-zone action and enter the domain you intend to host.
3. Review the result and open the new zone’s records.
4. Add or import the ordinary records the domain needs.
5. Check the assigned Azure nameservers and intended client binding.

Azure supplies its own apex NS and SOA records. Keep that authority information intact. Use the nameservers assigned to this zone, not another same-named zone or a generic Azure example.

Delegate through the registrar

Update the registrar’s nameserver settings to the assigned Azure set after the destination is ready. Microsoft’s delegation tutorial explains the separation between creating the zone, adding records and delegating the domain.

Keep the previous DNS answering through the resolver transition where applicable. Check authoritative answers, then the website, HTTPS and mail service separately. A successful provider write does not expire records already cached by visitors.

For a signed domain, plan the parent DS/signing transition using the DNSSEC guide. If creation times out, reconcile whether the zone already exists before repeating it; a provider response can be uncertain after a successful write.

See the PD Azure DNS Blesta guide for related tasks, or explore the module.