You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently using ExternalDNS version v0.13.5 with the Oracle Cloud Infrastructure (OCI) provider, and I'm experiencing an unusual issue. Specifically, ExternalDNS is creating an additional TXT record for each A record it creates, where the additional TXT record has an a- prefix on the hostname.
For example, for a Kubernetes service named nginx-test, it creates an A record for nginx-test.wlp.external-dns-test.com and two TXT records, one for nginx-test.wlp.external-dns-test.com and another for a-nginx-test.wlp.external-dns-test.com. Both TXT records are associated with the same Kubernetes service.
I verified that there are no duplicate services with the same name in different namespaces, no additional instances of ExternalDNS running, and no other configuration or template that could be causing the additional a- prefixed hostnames. Also, there are no automatic Ingress resources created for the LoadBalancer type services in the Kubernetes cluster.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm currently using ExternalDNS version v0.13.5 with the Oracle Cloud Infrastructure (OCI) provider, and I'm experiencing an unusual issue. Specifically, ExternalDNS is creating an additional TXT record for each A record it creates, where the additional TXT record has an
a-
prefix on the hostname.For example, for a Kubernetes service named
nginx-test
, it creates an A record fornginx-test.wlp.external-dns-test.com
and two TXT records, one fornginx-test.wlp.external-dns-test.com
and another fora-nginx-test.wlp.external-dns-test.com
. Both TXT records are associated with the same Kubernetes service.I verified that there are no duplicate services with the same name in different namespaces, no additional instances of ExternalDNS running, and no other configuration or template that could be causing the additional
a-
prefixed hostnames. Also, there are no automatic Ingress resources created for theLoadBalancer
type services in the Kubernetes cluster.Here are example logs from the ExternalDNS pod:
Any help or guidance to clarify this would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions