Description of problem: When External DNS adding A and TXT record to the Google Cloud DNS, an extra prefix "external-dns-" is added to the TXT record and cause the inconsistency between A and TXT records. e.g. external-dns-service-unsecure.example.com. TXT service-unsecure.example.com. A OpenShift release version: 4.10.0-0.nightly-2021-11-15-034648 Cluster Platform: GCP How reproducible: 100% Steps to Reproduce (in detail): 1. Install External DNS operator (see README.md of https://github.com/openshift/external-dns-operator/) 2. create secret and CR externaldns sample-gcp 3. create pod,svc 4. oc annotate svc <svc_name> external-dns.mydomain.org/publish="yes" 5. check the Google Cloud DNS and logs of externaldns pod Actual results: $ oc -n external-dns logs external-dns-sample-gcp-6d54d4bb99-cnxvd <---snip---> time="2021-11-16T10:13:38Z" level=info msg="Change zone: hongli-gc16-fv6sc-private-zone batch #0" time="2021-11-16T10:13:38Z" level=info msg="Add records: external-dns-service-unsecure.hongli-gc16.qe.gcp.devcluster.openshift.com. TXT [\"heritage=external-dns,external-dns/owner=external-dns-sample-gcp,external-dns/resource=service/hongli/service-unsecure\"] 300" time="2021-11-16T10:13:38Z" level=info msg="Add records: service-unsecure.hongli-gc16.qe.gcp.devcluster.openshift.com. A [172.30.205.231] 300" Expected results: should not add the prefix "external-dns-" to the TXT record, please keep the same name for the two kinds of records Impact of the problem: it might cause confusion Additional info: Tested with AWS Route 53 as well but didn't see the issue ** Please do not disregard the report template; filling the template out as much as possible will allow us to help you. Please consider attaching a must-gather archive (via `oc adm must-gather`). Please review must-gather contents for sensitive information before attaching any must-gathers to a bugzilla report. You may also mark the bug private if you wish.
Setting blocker+ because we don't want to ship the operator with this issue.
tested with latest external-dns-operator on AWS, Azure and GCG and always can see the prefix "external-dns-" is added for TXT records. According to Comment #4, now the behavior is the same on all the providers so I moving this to verified. Thanks.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of ExternalDNS Operator on OperatorHub), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2022:0781