GoDaddy DNS is not updating

[artem-zinnatullin]

What happened: I've been using external-dns for about half a year now with GoDaddy and it either adds additional A record without removing previous one or just never updates A record when my k8s cluster is experiencing auto-update and rotates public IP address.

What you expected to happen: external-dns should update A entry correctly with GoDaddy.

How to reproduce it (as minimally and precisely as possible):

            - --source=ingress
            - --domain-filter=mywebsite.com
            - --provider=godaddy
            - --interval=30m
            - --registry=txt
            - --txt-prefix=ed-

Anything else we need to know?:

This has been the case since release v0.10.2 all the way to current latest v0.12.2, I was hoping with changes in 0.12.2 with regards to TXT records it will finally start working but no..

In fact, I don't see a TXT entry created by external-dns.

Environment:

• External-DNS version (use external-dns --version): 0.12.2
• DNS provider: GoDaddy

Logs after update to 0.12.2 when I noticed that my cluster updated IP address and needs a DNS update:

time="2022-08-07T13:31:45Z" level=info msg="Instantiating new Kubernetes client"
time="2022-08-07T13:31:45Z" level=info msg="Using inCluster-config based on serviceaccount-token"
time="2022-08-07T13:31:45Z" level=info msg="Created Kubernetes client https://10.245.0.1:443"
time="2022-08-07T13:31:51Z" level=info msg="GoDaddy: 1 zones found"
time="2022-08-07T13:31:51Z" level=info msg="GoDaddy: Discard record @ for mywebsite.com is @ 1800 IN MX in1-smtp.messagingengine.com"
time="2022-08-07T13:31:51Z" level=info msg="GoDaddy: Discard record @ for mywebsite.com is @ 3600 IN MX in2-smtp.messagingengine.com"
time="2022-08-07T13:31:51Z" level=info msg="GoDaddy: 10 endpoints have been found"

It just didn't update an A entry in this case and my website experienced over 10h of downtime.