Unexpected TXT record with cname prefix #3255
Replies: 2 comments 1 reply
-
|
https://github.com/kubernetes-sigs/external-dns/blob/master/docs/registry.md Looks like they are changing the TXT registry format and it is keeping the old format for backward compatibility. |
Beta Was this translation helpful? Give feedback.
-
|
They don't seriously think this is a good idea right? Such a lame move to create a completely separate DNS record for a TXT record when DNS already supports it just fine. I mean if they want to give people the option to use this prefix way fine.. but please don't make it the "new" way thinking it's better somehow. |
Beta Was this translation helpful? Give feedback.
-
|
Hey guys, I'm having the same problem too, when I create an ingress external-dns identifies it correctly and creates an A type record, Does anyone have any idea how to solve this problem ? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have installed "external-dns" with
awsprovider and without settingtxtPrefixproperty. However, it's creating a TXT record withcname-preffix. For example, "external-dns" detects it has to create an alias (A) record my.domain.com, then it creates it but also creates my.domain.com (TXT) and cname-my.domain.com I would expect the latter not to be created since I didn't set thetxtPreffixproperty.Am I missing something? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions