kubernetes-sigs /external-dns
Configure external DNS servers dynamically from Kubernetes resources
★ 9,155⑂ 2,962👁 97⑃ 4,351● 2,452▤ 122
More from this author
+2
Daily
9,155
stars
2,962
forks
97
watchers
4,351
prs
2,452
issues
122
releases
README
--- hide: - toc - navigation --- ExternalDNS ExternalDNS synchronizes exposed Kubernetes Services and Ingresses with DNS providers. Documentation This README is a part of the complete documentation, available here and DeepWiki. What It Does Inspired by Kubernetes DNS, Kubernetes' cluster-internal DNS server, ExternalDNS makes Kubernetes resources discoverable via public DNS servers. Like KubeDNS, it retrieves a list of resources (Services, Ingresses, etc.) from the Kubernetes API to determine a desired list of DNS records. _Unlike_ KubeDNS, however, it's not a DNS server itself, but merely configures other DNS providers accordingly—e.g. AWS Route 53 or Google Cloud DNS. In a broader sense, ExternalDNS allows you to control DNS records dynamically via Kubernetes resources in a DNS provider-agnostic way. The FAQ contains additional information and addresses several questions about key concepts of ExternalDNS. To see ExternalDNS in action, have a look at this video or read this blogpost. Running ExternalDNS ExternalDNS allows you to keep selected zones (via --domain-filter) synchronized with Ingresses and Services of type=LoadBalancer and nodes in many DNS providers. See In-tree providers for the built-in list, and New providers for webhook-based ones. ExternalDNS is, by default, aware of the records it is managing, therefore it can safely manage non-empty hosted zones. We strongly encourage you to set --txt-owner-id to a unique value that doesn't change for the lifetime of your cluster. You might also want to run ExternalDNS in a dry run mode (--dry-run flag) to see the changes to be submitted to your DNS Provider API. Note that all flags can be replaced with environment variables; for instance, --dry-run could be replaced with EXTERNAL_DNS_DRY_RUN=1. ExternalDNS runs as a controller in your cluster, and can also be run locally to test a configuration. For provider-specific setup, see the In-tree providers table (each row links its tutorial) or the webhook providers. More tutorials — ingress controllers, sources, and provider extras — are in the full documentation. Running Locally See the contributor guide for details on compiling from source. Setup Steps Next, run an application and expose it via a Kubernetes Service: console kubectl run nginx --image=nginx --port=80 kubectl expose pod nginx --port=80 --target-port=80 --type=LoadBalancer Annotate the Service with your desired external DNS name. Make sure to change example.org to your domain. console kubectl annotate service nginx "external-dns.kubernetes.io/hostname=nginx.example.org." Optionally, you can customize the TTL value of the resulting DNS record by using the external-dns.kubernetes.io/ttl annotation: console kubectl annotate service nginx "external-dns.kubernetes.io/ttl=10" For more details on configuring TTL, see advanced ttl. Use the internal-hostname annotation to create DNS records with ClusterIP as the target. console kubectl anno
Top issues
#449Creating dns records for apex / root domains96 comments · 2018-01-26#2430support multiple replicas for reliability51 comments · 2021-11-11#1233AWS Route53 GovCloud Support44 comments · 2019-10-16#3977External DNS keeps upserting - v0.13.637 comments · 2023-10-09#4347Moving providers out of tree32 comments · 2024-03-28#5243Defining a path to Beta for DNSEndpoint API29 comments · 2025-04-01#1281[Feature Request] Support ClusterIP services with externalIPs set27 comments · 2019-11-18#3753Inconsistencies in semantics of --domain-filter between providers25 comments · 2023-06-29
Discussions
#6642Plan for the next Release?1 comments · 2026-08-18#6629Kubernetes - externalDNS crashing with function symbol table not sorted by PC offset: 0xa5f3e0 0x0 APIResourceDiscovery).String , plugin:1 comments · 2026-08-16#6469Make publishing of DNS record per pod optional for headless service0 comments · 2026-06-04#6195Does external-dns support the AWS European Sovereign Cloud (EUSC) region (THF)?0 comments · 2026-02-13#6191Is there a way to make two resources generate targets for the same Endpoint?1 comments · 2026-02-11#6170How to **not** install the DNSEndpoint CRD twice when using the Helm chart twice (for 2 different providers) on the same namespace ?3 comments · 2026-02-06#6126Do you have a plan to support AWS route53 healthcheck creating? Thanks.2 comments · 2026-01-19#6107Request new release including Go security fixes for golang.org/x/crypto and stdlib vulnerabilities0 comments · 2026-01-12
Latest release
v0.24.0 v0.24.0 2026-10-23General information
It's recommended to try this version with --dry-run=true first, see upgrade instructions.
Action required before upgrade
- :warning: gateway-tcproute source now watches TCPRoute v1 (6755).
- Requires Gateway API CRDs = v1.6.0.
- :warning: skipper-routegroup source now uses informers (6714): the RouteGroup CRD must be installed.
- :information_source: .Metadata in --fqdn-template is deprecated: use {{.Name}} instead of {{.Metadata.Name}}.
- :warning: DNSEndpoint and DNSRecord CRDs are now validated at admission (6620).
- Re-apply the CRDs. Existing object