RFC2136 (FreeIPA) DNS entries not removed when corresponding Kubernetes endpoints are deleted

[neverlless]

trafficstars

What happened: When using External-DNS in Kubernetes with Freeipa(rfc2136) as the DNS server, I noticed an issue where new DNS entries are created when a new endpoint appears. However, these DNS records are not removed when such an endpoint is deleted. There are no visible errors in the logs, only the addition operations are visible.

What you expected to happen: I expected the DNS entries corresponding to deleted endpoints to also be removed automatically by External-DNS.

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

1. Start a Kubernetes cluster with External-DNS set to use rfc2136 (Freeipa) as the DNS provider.
2. Create a service or ingress that causes External-DNS to create a new DNS record.
3. Delete the service or ingress.
4. Observe that the DNS entry created for it in step 2 is not removed.

Anything else we need to know?:

Environment:

• External-DNS version: 0.14.0
• DNS provider: Freeipa (rfc2136)
• Others: args - --metrics-address=:7979 --log-level=info --log-format=json --domain-filter=pp.local --policy=sync --provider=rfc2136 --registry=txt --interval=1m --txt-owner-id=dev-k8s --source=ingress --rfc2136-host=dns.pp.local --rfc2136-port=53 --rfc2136-zone=sl.local --rfc2136-min-ttl=0s --rfc2136-tsig-secret-alg=hmac-sha256 --rfc2136-tsig-keyname=external-dns-256

[k8s-triage-robot]

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

[dschemp]

I can only support this issue. Using RFC2136 with the DNS server in the Synology NAS. Removing any resource that would trigger the creation of DNS entries does nothing. Nothing is shown in the logs apart from "All records are already up to date"

[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

[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

[k8s-ci-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.