Epic Goal

• Today, the Multi-Arch libvirt CI uses coredns

As discussed in to https://redhat-internal.slack.com/archives/C017UFPQA4X/p1761240479219999 , we propose to switch to use real DNS domains to account for name resolution off cluster.

Why is this important?

• Eliminate a single point of failure with CoreDNS, push nameresolution into a reliable stack independent of local looks ups.

Scenarios
1. 

Acceptance Criteria

• Name resolution works outside of build01
• Power CI works
• Z CI works
•  
• .
• Dependencies (internal and external)

1.Multi-Arch Haproxy 

2. Release configuration 

3. dnsConfig 
https://github.com/openshift/release/blob/master/ci-operator/step-registry/openshift/e2e/libvirt/upi/openshift-e2e-libvirt-upi-workflow.yaml
Previous Work (Optional):
1. …

Open questions::
1. …

Done Checklist

• CI - For new features (non-enablement), existing Multi-Arch CI jobs are not broken by the Epic
• Release Enablement: <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - If the Epic is adding a new stream, downstream build attached to advisory: <link to errata>
• QE - Test plans in Test Plan tracking software (e.g. Polarion, RQM, etc.): <link or reference to the Test Plan>
• QE - Automated tests merged: <link or reference to automated tests>
• QE - QE to verify documentation when testing
• DOC - Downstream documentation merged: <link to meaningful PR>
• All the stories, tasks, sub-tasks and bugs that belong to this epic need to have been completed and indicated by a status of 'Done'.