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

Documentation feedback: Add an example for an internal DNS scenario for Designate

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • rhos-17.1.3
    • documentation
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • ?
    • ?
    • None
    • Low

      https://docs.redhat.com/en/documentation/red_hat_openstack_platform/17.1/html/configuring_dns_as_a_service/intro-dns-service_rhosp-dnsaas#dns-service-common-deploy-scenario_intro-dns-service

      I think we may be missing the most common scenario our customers would be looking to use Designate for: A non-public facing DNS for internal DNS resolution of their resources.
      At least I've been already a couple of cases where customers would want to deploy zones like cloud.example.internal.
      Our examples all rely on how top level domain resolution would search for a .com or .org TLD.

      Here you have 2 case examples of such requests: 03806176 and 03951623

              grakausk@redhat.com Greg Rakauskas
              rhn-support-jveiraca1 Joaquin Veira
              rhos-dfg-networking-squad-vans
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: