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.52k stars 2.53k forks source link

MX record for cloudflare gives error 1004 #4207

Closed davhdavh closed 1 week ago

davhdavh commented 7 months ago

What happened:

time="2024-01-25T08:17:24Z" level=error msg="failed to create record: DNS Validation Error (1004)" action=CREATE record=sub.site.com ttl=24400 type=MX zone=695519de960b61159af007646f57da9d

What you expected to happen:

Mx was created.

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

apiVersion: externaldns.k8s.io/v1alpha1
kind: DNSEndpoint
metadata:
  name: mx
  namespace: myns
spec:
  endpoints:
    - dnsName: sub.site.com
      recordTTL: 24400
      recordType: MX
      targets:
        - 10 sub.site.com

Anything else we need to know?:

TXT for DKIM using DNSEndpoint, A for ingress, TXT for SPF using DNSEndpoint all work just fine, so problem is specific to MX. Manually creating record in cloudflare UI works.

Environment:

k8s-triage-robot commented 4 months ago

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

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

You can:

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

/lifecycle stale

davhdavh commented 3 months ago

I would submit a PR, if anyone could point me in the right direction

james-callahan commented 3 months ago

I'm getting the same error. @jacobbednarz maybe you could help?

jacobbednarz commented 3 months ago

i'm sorry but this lacks enough information for me as an outsider to be able to debug the issue. in general though, this API error points at the payload you have provided in not valid for the record type you requested. what do the HTTP interactions look like here?

james-callahan commented 3 months ago

in general though, this API error points at the payload you have provided in not valid for the record type you requested.

I guess that the MX records are passed as 10 sub.site.com in the Content field: https://github.com/kubernetes-sigs/external-dns/blob/fa17f9d06cbfe3315430529151324fae5a421e43/provider/cloudflare/cloudflare.go#L446 and the fix is that it needs to be passed as multiple/different arguments?

k8s-triage-robot commented 2 months ago

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:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 month ago

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:

You can:

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

/close not-planned

k8s-ci-robot commented 1 month ago

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

In response to [this](https://github.com/kubernetes-sigs/external-dns/issues/4207#issuecomment-2213098756): >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][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
james-callahan commented 1 month ago

/reopen

k8s-ci-robot commented 1 month ago

@james-callahan: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to [this](https://github.com/kubernetes-sigs/external-dns/issues/4207#issuecomment-2213171507): >/reopen 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
davhdavh commented 1 month ago

/reopen

k8s-ci-robot commented 1 month ago

@davhdavh: Reopened this issue.

In response to [this](https://github.com/kubernetes-sigs/external-dns/issues/4207#issuecomment-2221773507): >/reopen 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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.
k8s-triage-robot commented 1 week ago

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:

You can:

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

/close not-planned

k8s-ci-robot commented 1 week ago

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

In response to [this](https://github.com/kubernetes-sigs/external-dns/issues/4207#issuecomment-2278924431): >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][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[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-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.