Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-8125

What to do about making the unbound resolver accessible?

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • designate-operator
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • OSPRH-4410 - Designate support for RHOSO Greenfield Deployment (Target 18.0 FR3)
    • ?
    • ?

      The unbound resolver is meant to be used as part of the neutron-dns integration solution and must be accessible by the tenant VMs in the openstack cloud. How can this be achieved? Does the unbound resolver also need to be accessible to DNS clients outside of the podified control plane? If so, are there any constraints on this?

              Unassigned Unassigned
              rhn-engineering-beagles Brent Eagles
              rhos-dfg-networking-squad-vans
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: