PD Azure DNS manages public DNS zones from one configured resource group per provider connection. If zones are missing, check placement and access before creating another copy or changing the domain’s nameservers.

Compare the connection and zone

1. Open Azure DNS → Providers and identify the selected connection.
2. Confirm its tenant, application, subscription and resource-group name.
3. Check where the intended public DNS zone actually lives in Azure.
4. Return to Azure DNS → Zones and select the corresponding provider.
5. Compare a known zone and record before enabling customer access.

A successful connection test uses a subscription-level list request. Normal browsing uses the configured group. These are different checks: a successful test does not mean every zone across the subscription is included in this connection.

Prepare a group deliberately

Use an existing group authorised for this DNS connection where possible. The module can attempt to create a missing group when creating a zone, but that operation needs resource-group write permission. DNS Zone Contributor alone does not grant general group creation.

Ask the Azure administrator to create the group or review that distinct operation instead of broadening every DNS credential. A resource-group location describes the group’s metadata; public Azure DNS service is global.

Separate multiple connections

For another subscription or a separate zone group, configure and test the intended provider connection with its own placement and access. Keep the provider labels clear so the same domain in different groups is not mistaken for a single authoritative zone.

This module’s public-zone workflow is not Azure Private DNS/VNet management. Check that you are looking for the right kind of DNS resource before treating an empty list as a failed install.

If access is refused, preserve the exact action and scope for the Azure administrator. If the zone is present but visitors see different answers, move on to the delegation checks; do not recreate working DNS just to refresh the list.

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