Scenario 5: Guest dns.cluster Config Includes Both Zones

Objective: Verify that the guest cluster's dns.cluster resource includes both public and private zones, even for Private topology. This confirms that publicZoneID is correctly propagated from the HostedCluster through the CPO to the guest's DNS configuration.

Step	Check	Result	Evidence
1	spec.publicZone is present with correct zone ID	PASS	Points to os4-common public DNS zone
2	spec.privateZone is present with correct zone ID	PASS	Points to brcox-100054-hc.hcp-sm-azure... private DNS zone
3	spec.baseDomain is correctly formed	PASS	brcox-100054-hc.hcp-sm-azure.azure.devcluster.openshift.com

Commands & Outputs

Steps 1-3: Guest dns.cluster resource (via port-forward to KAS)

$ kubectl get dns cluster -o json | jq .spec
{
  "baseDomain": "brcox-100054-hc.hcp-sm-azure.azure.devcluster.openshift.com",
  "platform": {
    "type": ""
  },
  "privateZone": {
    "id": "/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"
  },
  "publicZone": {
    "id": "/subscriptions/237432b9-9dc5-4b0b-b058-8868ac6a774b/resourceGroups/os4-common/providers/Microsoft.Network/dnszones/hcp-sm-azure.azure.devcluster.openshift.com"
  }
}