mirror of
https://github.com/kubernetes-sigs/external-dns.git
synced 2026-04-03 23:21:01 +02:00
b9aba54e8f
* Support MX record with trailing dot * refactor(crd): Replace nested if statements with switch case; add test for target without trailing dot
29 lines
1001 B
Markdown
29 lines
1001 B
Markdown
# MX record with CRD source
|
|
|
|
You can create and manage MX records with the help of [CRD source](../sources/crd.md)
|
|
and `DNSEndpoint` CRD. Currently, this feature is only supported by `aws`, `azure`, `cloudflare`, `digitalocean`, `google` and `webhook` providers.
|
|
|
|
In order to start managing MX records you need to set the `--managed-record-types=MX` flag.
|
|
|
|
```console
|
|
external-dns --source crd --provider {aws|azure|google|digitalocean} --managed-record-types=A --managed-record-types=CNAME --managed-record-types=MX
|
|
```
|
|
|
|
Targets within the CRD need to be specified according to the RFC 1034 (section 3.6.1). Below is an example of
|
|
`example.com` DNS MX record which specifies two separate targets with distinct priorities.
|
|
|
|
```yaml
|
|
apiVersion: externaldns.k8s.io/v1alpha1
|
|
kind: DNSEndpoint
|
|
metadata:
|
|
name: examplemxrecord
|
|
spec:
|
|
endpoints:
|
|
- dnsName: example.com
|
|
recordTTL: 180
|
|
recordType: MX
|
|
targets:
|
|
- 10 mailhost1.example.com
|
|
- 20 mailhost2.example.com
|
|
```
|