A bad DNS Services instance (pre-provisioning, etc.), aka not Active, can cause failures when trying to identify the proper instance and zone for a specific baseDomain.

    4.14.11

    Requires a bad DNS Services instance (one in pre-provisioning for instance) to reproduce 100% 

    1. Create a DNS Services instance in a bad state
    2. Run IPI using a healthy DNS Service and baseDomain
    

    FATAL failed to fetch Install Config: failed to fetch dependency of "Install Config": failed to generate asset "Base Domain": no domain names found in project

or

    FATAL failed to fetch Metadata: failed to fetch dependency of "Metadata": failed to fetch dependency of "Bootstrap Ignition Config": failed to fetch dependency of "CVO Ignore": failed to fetch dependency of "Common Manifests": failed to generate asset "DNS Config": failed to get DNS zone ID: Access to the api resource is not authorized.

    Successful IPI install (ignore bad DNS Services instance) or legitimate failure trying to use bad/wrong domain

    IBM Cloud will be looking at resolving this issue. I may be unable to replicate the error unless I can find a method to create a bad DNS Services instance that could replicate this error.

At best, I think filtering the list of DNS Services instances to those that are healthy would be a minimum fix, additional logic and error handling would be nice, but might be difficult to test and verify if I cannot find an easy method to replicate this failure.