search

kubernetes-sigs / external-dns

Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
Apache License 2.0
7.76k stars 2.59k forks source link

Bug in Infoblox TXT records #1986

Closed aelbarkani closed 3 years ago

aelbarkani commented 3 years ago

What happened:

We have this error in external dns: time="2021-03-02T08:36:25Z" level=debug msg="Skipping endpoint dev.www.apps.ocp-1.pin.prd.mlb.nbyt.fr 0 IN A 10.110.134.25 [] because owner id does not match, found: \"\", required: \"default\"" time="2021-03-02T08:36:25Z" level=debug msg="Skipping endpoint dev.www.apps.ocp-1.pin.prd.mlb.nbyt.fr 0 IN CNAME apps.ocp-1.pin.prd.mlb.nbyt.fr [] because owner id does not match, found: \"\", required: \"default\""

This happened because we switched from an Ingress Controller that adds hostname in status to an Ingress Controller that adds ip address (from a CNAME record to an A record in external-dns). It seems like the format of TXT record when the Ingress has hostname status is not right in Infoblox.

What you expected to happen:

The DNS records to be updated smoothly when hostname or IP changes.

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

Anything else we need to know?:

N/A

Environment:

jgrumboe commented 3 years ago

Hi, I used Infoblox some time ago and it worked fine. But I was using --txt-suffix also. Do you use a txt-prefix or txt-suffix option? (One of these is manadatory when using CNAMEs.)

kbreit commented 3 years ago

@aelbarkani have you been able to resolve this? I'm seeing the same error but maybe different cause in RFC2136 provider when using Istio gateways.

jgrumboe commented 3 years ago

Update: Forget my last comment! I haven't read the error message correctly.

I think that should be the correct answer: because owner id does not match, found: \"\", required: \"default\"" is about missing or wrong --txt-owner-id. The message states that there is already a TXT record for a given A or CNAME and the TXT-record has set an owner-id = "default", your external-dns instance is running with an empty --txt-owner-id. Try setting it to "default" to take ownership of these records (be aware of already managed records may loose ownership), modify the TXT record to reflect the owner id of your current setup or delete the TXT record (external-dns will recreate it after taking owner ship).

k8s-triage-robot commented 3 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 3 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 3 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/close

k8s-ci-robot commented 3 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/external-dns/issues/1986#issuecomment-980643750): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues and PRs 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 or PR with `/reopen` >- Mark this issue or PR as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.