Description
What happened:
Applied the following DNSEndpoint resource:
apiVersion: externaldns.k8s.io/v1alpha1
kind: DNSEndpoint
metadata:
name: examplednsrecord
spec:
endpoints:
- dnsName: foo.bar.com
recordTTL: 180
recordType: TXT
targets:
- "test"
This results in no resource created. Even in debug mode, there is no object even mentioned.
As soon as I kubectl edit dnsendpoint examplednsrecord to change it from TXT to CNAME I see the following output.
{"level":"debug","msg":"Adding foo.bar.com. to zone ffxblue.io. [Id: /hostedzone/...]","time":"2020-06-25T08:40:24Z"}
{"level":"debug","msg":"Adding foo-txt.bar.com. to zone ffxblue.io. [Id: /hostedzone/...]","time":"2020-06-25T08:40:24Z"}
{"level":"info","msg":"Desired change: CREATE foo.bar.com CNAME [Id: /hostedzone/...]","time":"2020-06-25T08:40:24Z"}
{"level":"info","msg":"Desired change: CREATE foo-txt.bar.com TXT [Id: /hostedzone/..]","time":"2020-06-25T08:40:24Z"}
What you expected to happen:
It is expected that the DNSEndpoint should be able to create all record types. The comments in the source code specifically list SRV and TXT records. My initially attempts were a MX record which also failed.
Attempting to use the providerSpecific options to create the exact record also did not work.
How to reproduce it (as minimally and precisely as possible):
Apply the YAML I provided at the start of this issue and change the dnsName to be a valid zone that external-dns is managing.
All my tests have been using AWS. Uncertain if this is an issue with other providers.
Anything else we need to know?:
Environment:
- External-DNS version (use
external-dns --version): 0.7.2 - DNS provider: AWS
- Others:
- The option
preferCNAMEenabled. - Policy set to
sync. - Using the Bitnami Helm chart.
- The option
Activity