After creating an additional Ingress Controller, the Ingress CO goes into a degraded state

Issue

• After creating an additional Ingress Controller, the Ingress Cluster Operator goes into a degraded state.

  $ oc get ingresscontrollers <ingresscontroller_name> -oyaml
  - lastTransitionTime: '2023-06-29T03:30:07Z'
  message: 'The record failed to provision in some zones: [{ map[Name:ocp4-xxx-int
    kubernetes.io/cluster/ocp4-xxx:owned]}]'
  reason: FailedZones
  status: 'False'
  type: DNSReady
  - lastTransitionTime: '2023-06-29T03:30:49Z'
  message: 'One or more status conditions indicate unavailable: DNSReady=False (FailedZones:
    The record failed to provision in some zones: [{ map[Name:ocp4-xxx-int kubernetes.io/cluster/ocp4-xxx:owned]}])'
  reason: IngressControllerUnavailable
  status: 'False'
  type: Available
  - lastTransitionTime: '2023-06-29T03:30:03Z'
  status: 'False'
  type: Progressing
   - lastTransitionTime: '2023-06-29T03:30:49Z'
  message: 'One or more other status conditions indicate a degraded state: DNSReady=False
    (FailedZones: The record failed to provision in some zones: [{ map[Name:ocp4-xxx-int
    kubernetes.io/cluster/ocp4-djm5t:owned]}])'
  reason: DegradedConditions
  status: 'True'
  type: Degraded