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.73k stars 2.58k forks source link

Cannot create cloudflare ipv6 records #2625

Closed michaelsstuff closed 2 years ago

michaelsstuff commented 2 years ago

What happened: Set up a domain in cloudflare. annotation is on an ingress controller (treafik) It does set the ipv4 just fine. But it does not create an ipv6 record (ingress has both)

Only hint at a problem with v6 comes with debug:

time="2022-02-24T13:27:47Z" level=error msg="failed to create record: error from makeRequest: HTTP status 400: content \"{\\\"result\\\":null,\\\"success\\\":false,\\\"errors\\\":[{\\\"code\\\":1004,\\\"message\\\":\\\"DNS Validation Error\\\",\\\"error_chain\\\":[{\\\"code\\\":9005,\\\"message\\\":\\\"Content for A record must be a valid IPv4 address.\\\"}]}],\\\"messages\\\":[]}\"" action=CREATE record=staging.mydomain.net ttl=1 type=A zone=xxxxxxxxxxxxxxxxxxxxxxxxxxx

What you expected to happen: I would expect it to either not try at all or create the ipv6 if is there.

How to reproduce it (as minimally and precisely as possible): Follow https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/cloudflare.md, but add an ipv6 to your ingress controller.

Anything else we need to know?:

Environment:

danopia commented 2 years ago

Unfortunately, the external-dns project does not yet support making IPv6 addresses into AAAA records. Here's some existing tickets:

k8s-triage-robot commented 2 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 2 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 2 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 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes-sigs/external-dns/issues/2625#issuecomment-1195792627): >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.