Scenario 4: Private DNS Zone Naming

Objective: Verify the private DNS zone uses the correct naming format {name}.{baseDomain} instead of the old {name}-azurecluster.{baseDomain}.

Overall Scenario 4: PASS — Both checks verified.
StepCheckResultEvidence
1 New naming format zone exists: {name}.{baseDomain} PASS Zone brcox-100054-hc.hcp-sm-azure.azure.devcluster.openshift.com confirmed in RG
2 HostedCluster privateZoneID uses new naming PASS {name}.{baseDomain} format, not {name}-azurecluster.{baseDomain}

Commands & Outputs

Step 1: List private DNS zones in infra RG

$ az network private-dns zone list --resource-group brcox-100054-hc-brcox-100054 --query '[].name' -o tsv

brcox-100054-hc-azurecluster.hcp-sm-azure.azure.devcluster.openshift.com   # old naming (created by CAPZ)
brcox-100054-hc.hcp-sm-azure.azure.devcluster.openshift.com               # new naming (created by hypershift CLI)
brcox-100054-hc.hypershift.local                                           # internal hypershift zone
hcp-sm-azure.azure.devcluster.openshift.com                               # parent zone link

Step 2: Verify privateZoneID on HostedCluster

$ oc get hostedcluster brcox-100054-hc -n clusters -o jsonpath='{.spec.dns}' | jq .
{
  "baseDomain": "hcp-sm-azure.azure.devcluster.openshift.com",
  "privateZoneID": "/subscriptions/237432b9-9dc5-4b0b-b058-8868ac6a774b/resourceGroups/brcox-100054-hc-brcox-100054/providers/Microsoft.Network/privateDnsZones/brcox-100054-hc.hcp-sm-azure.azure.devcluster.openshift.com",
  "publicZoneID": "/subscriptions/237432b9-9dc5-4b0b-b058-8868ac6a774b/resourceGroups/os4-common/providers/Microsoft.Network/dnszones/hcp-sm-azure.azure.devcluster.openshift.com"
}
Note: The old -azurecluster zone still exists because it is created by CAPZ (Cluster API for Azure), which uses a different naming convention. The HyperShift infra command now creates the correct {name}.{baseDomain} zone, and the hypershift destroy infra azure command handles cleanup of both naming formats.
← Scenario 3 Scenario 5 →