flywithu/community-catalog
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
community-catalog/infra-templates/dnsupdate-rfc2136/4/README.md

2.4 KiB
Raw Blame History

DNS Update (RFC2136)

Rancher External DNS service powered by any RFC2136 compatible DNS server

Changelog

v0.6.2
  • Adds support for disabling/enforcing external DNS on the host and service level using labels
  • Adds support for insecure DNS Updates
  • Fixes an issue with lingering TCP keep-alive connections to the Rancher Metadata service

Usage

Upgrade Notes

While upgrading from a version lower than v0.6.0 the TTL configuration value should not be changed. You may change it once the upgrade has been completed.

Limitation when running the service on multiple Rancher servers

When running multiple instances of the External DNS service configured to use the same domain name, then only one of them can run in the "Default" environment of a Rancher server instance.

Supported host labels

io.rancher.host.external_dns_ip
Override the IP address used in DNS records for containers running on the host. Defaults to the IP address the host is registered with in Rancher.

io.rancher.host.external_dns
Accepts 'true' (default) or 'false'
When this is set to 'false' no DNS records will ever be created for containers running on this host.

Supported service labels

io.rancher.service.external_dns
Accepts 'always', 'never' or 'auto' (default)

  • always: Always create DNS records for this service
  • never: Never create DNS records for this service
  • auto: Create DNS records for this service if it exposes ports on the host

io.rancher.service.external_dns_name_template Accepts valid DNS name template

By default DNS entries are named based on default template defined on dnsupdate service. You can customize it per service by assigning io.rancher.service.external_dns_name_template label to each service. dnsupdate will use this template instead of default one when creating dns record for related service.

Custom DNS name template

By default DNS entries are named <service>.<stack>.<environment>.<domain>.
You can specify a custom name template used to construct the subdomain part (left of the domain/zone name) of the DNS records. The following placeholders are supported:

  • %{{service_name}}
  • %{{stack_name}}
  • %{{environment_name}}

Example:

%{{stack_name}}-%{{service_name}}.statictext

Make sure to only use characters in static text and separators that your provider allows in DNS names.