mirrors/external-dns
1
0
Fork 0
mirror of https://github.com/kubernetes-sigs/external-dns.git synced 2025-08-07 18:16:57 +02:00
Code Issues Packages Projects Releases Wiki Activity

add documentation about canonical hosted zones

Browse Source
This commit is contained in:
Jeff Wenzbauer 2023-02-22 13:45:19 -07:00
parent 94d72a5ca8
commit 31f06153f6
No known key found for this signature in database
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/tutorials/aws.md
View File

@ -837,6 +837,14 @@ You can configure Route53 to associate DNS records with healthchecks for automat
Note: ExternalDNS does not support creating healthchecks, and assumes that `<health-check-id>` already exists. Note: ExternalDNS does not support creating healthchecks, and assumes that `<health-check-id>` already exists.
## Canonical Hosted Zones
When creating ALIAS type records in Route53 it is required that external-dns be aware of the canonical hosted zone in which
the specified hostname is created. External-dns is able to automatically identify the canonical hosted zone for many
hostnames based upon known hostname suffixes which are defined in [aws.go](../../provider/aws/aws.go). If a hostname
does not have a known suffix then the suffix can be added into `aws.go` or the [target-hosted-zone annotation](#target-hosted-zone)
can be used to manually define the ID of the canonical hosted zone.
## Govcloud caveats ## Govcloud caveats
Due to the special nature with how Route53 runs in Govcloud, there are a few tweaks in the deployment settings. Due to the special nature with how Route53 runs in Govcloud, there are a few tweaks in the deployment settings.