Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-819

[ExtDNS] Invalid TXT records for wildcard domains on Azure

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.11.z
    • Networking / DNS
    • Important
    • None
    • Sprint 224, Sprint 225, Sprint 226, Sprint 227
    • 4
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      The new ExternalDNS TXT record format generates wildcard TXT records which don't adhere to AzureDNS standard.
      The creation of the target DNS records (A/CNAME) becomes impossible for the wildcard records on AzureDNS.
      The fix has added the flag to the managed ExternalDNS instances to replace the wildcard character "*" with a text equivalent.
      As a result the wildcard DNS records can be created on AzureDNS.
      Show
      The new ExternalDNS TXT record format generates wildcard TXT records which don't adhere to AzureDNS standard. The creation of the target DNS records (A/CNAME) becomes impossible for the wildcard records on AzureDNS. The fix has added the flag to the managed ExternalDNS instances to replace the wildcard character "*" with a text equivalent. As a result the wildcard DNS records can be created on AzureDNS.
    • Bug Fix
    • In Progress

      Description of problem:

      Azure DNS enforces the standard about the wildcard records: the asterisk character has to be the leftmost character of the DNS record.
With the new TXT format introduced in ExternalDNS Operator 1.0.0, the TXT records are prefixed with the record type ("a-", "cname-", etc.) which doesn't conform to the Azure DNS restriction.

      Version-Release number of selected component (if applicable):

      1.0.0

      How reproducible:

      - Create ExternalDNS CR with Azure provider and Service source
- Create a Kubernetes service with hostname annotation set to a a wildcard hostname

       

      Steps to Reproduce:

      1.Create ExternalDNS CR with Azure provider and Service source
2.Create a Kubernetes service with hostname annotation set to a a wildcard hostname

      Actual results:

      ExternalDNS operand fails to create DNS records for the service having wildcard as hostname. Errors are logged in ExternalDNS operand.

      Expected results:

      ExternalDNS operand has to be able to create DNS records (A/CNAME and TXT).

      Additional info:

      Upstream GitHub issue: https://github.com/kubernetes-sigs/external-dns/issues/2922

              alebedev@redhat.com Andrey Lebedev
              alebedev@redhat.com Andrey Lebedev
              Hongan Li Hongan Li
              Servesha Dudhgaonkar Servesha Dudhgaonkar
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: