external-dns rfc2136 provider timeout error if registry TXT DNS record exceeds 37 characters

It seems that the maximum amount of characters that can be set, at least for the rfc2136 provider, is 35 (37 chars if you also count the prefix/suffix for the TXT record). If any longer name is used, it will log a timeout. .

Once I disable the TXT registry it (noop) then it works without any issue.

for example when using this name: persistentxvolumes.emea.dev.k8s.corp (36 chars)

time="2022-11-30T16:55:56Z" level=debug msg="AddRecord.ep=persistentxvolumes.emea.dev.k8s.corp 0 IN A  172.17.20.10 []"
time="2022-11-30T16:55:56Z" level=info msg="Adding RR: persistentxvolumes.emea.dev.k8s.corp 0 A 172.17.20.10"
time="2022-11-30T16:55:56Z" level=debug msg="AddRecord.ep=persistentxvolumes.emea.dev.k8s.corp 0 IN TXT  \"heritage=external-dns,external-dns/owner=devk8s,external-dns/resource=ingress/demo-persistentvolume/persistentvolume2-ing\" []"
time="2022-11-30T16:55:56Z" level=info msg="Adding RR: persistentxvolumes.emea.dev.k8s.corp 0 TXT \"heritage=external-dns,external-dns/owner=devk8s,external-dns/resource=ingress/demo-persistentvolume/persistentvolume2-ing\""
time="2022-11-30T16:55:56Z" level=debug msg="AddRecord.ep=a-persistentxvolumes.emea.dev.k8s.corp 0 IN TXT  \"heritage=external-dns,external-dns/owner=devk8s,external-dns/resource=ingress/demo-persistentvolume/persistentvolume2-ing\" []"
time="2022-11-30T16:55:56Z" level=info msg="Adding RR: a-persistentxvolumes.emea.dev.k8s.corp 0 TXT \"heritage=external-dns,external-dns/owner=devk8s,external-dns/resource=ingress/demo-persistentvolume/persistentvolume2-ing\""
time="2022-11-30T16:55:56Z" level=debug msg=SendMessage
time="2022-11-30T16:55:58Z" level=warning msg="warn in dns.Client.Exchange: read udp 10.42.10.180:33202->172.17.1.10:53: i/o timeout"
time="2022-11-30T16:55:58Z" level=debug msg=SendMessage.success

As soon as I remove one char from the name, it works fine.

What you expected to happen: To be created and respect the 64 character limit

How to reproduce it (as minimally and precisely as possible): Within a K8s cluster with external-dns enabled, create an ingress with a host that has more than 40 characters (including the dots).

Environment:

External-DNS version (use external-dns --version): v0.13.1
DNS provider: rfc2136
no TXT prefix/suffix, so the tool ads 2 characters within the second TXT record: 'a-'

Nov 30 '22 17:11 rhessing

/retitle Improper error message for character limit of 40 chars

Nov 30 '22 19:11 kundan2707

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Feb 28 '23 19:02 k8s-triage-robot

Pretty sure this is still an issue.

/remove-lifecycle stale

Mar 01 '23 01:03 ruifung

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

May 30 '23 01:05 k8s-triage-robot

/remove-lifecycle stale

May 30 '23 10:05 ruifung

Likely related to/the same bug as #3836.

Aug 01 '23 22:08 Protryon

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Jan 25 '24 16:01 k8s-triage-robot

/remove-lifecycle stale

Jan 25 '24 18:01 rhessing

@rhessing Is this actually still an issue though?

Where previously it would exhibit the aforementioned behavior, After #3836 and #3837 I have the TXT registry enabled on my setup with no issues.

I'm currently on version 0.14.0

Jan 26 '24 16:01 ruifung

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle stale
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

Apr 25 '24 17:04 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Mark this issue as fresh with /remove-lifecycle rotten
Close this issue with /close
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

May 25 '24 17:05 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied
After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen
Mark this issue as fresh with /remove-lifecycle rotten
Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Jun 24 '24 17:06 k8s-triage-robot

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

After 90d of inactivity, lifecycle/stale is applied

After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied

After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

Reopen this issue with /reopen

Mark this issue as fresh with /remove-lifecycle rotten

Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Jun 24 '24 17:06 k8s-ci-robot