Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

ExternalDNS review

Free#12 of 25 in DNS Management Software

A focused, open-source controller for automating DNS records from Kubernetes resources.

7.7/10Editor score
ExternalDNS7.7 Visit ExternalDNS

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

ExternalDNS is an open-source Kubernetes controller for creating and updating DNS records from Services, Ingresses, Gateway API routes, and custom resources. It is designed for Kubernetes teams that want DNS changes to follow application resources rather than managing records separately. ExternalDNS is not a DNS server or a hosted DNS management service; it connects Kubernetes to supported DNS providers and applies configured record-management policies.

The integration scope is a central strength. Provider adapters support AWS Route 53, AWS Cloud Map, Azure DNS, Cloudflare, CoreDNS, DNSimple, Google Cloud DNS, GoDaddy, Linode DNS, NS1, Oracle Cloud Infrastructure DNS, OVHcloud, PowerDNS, Pi-hole, and RFC2136. Teams can discover records from Kubernetes resources and custom resources, restrict management to selected domains, and use create-only, upsert-only, or sync policies. Additional provider integrations can connect through an HTTP webhook interface, while Prometheus metrics are exposed through a metrics endpoint.

Operational controls make ExternalDNS useful where record ownership and change visibility matter. Dry-run mode lets teams preview DNS changes, and TXT, CRD, DynamoDB, and other registries can track ownership. The free, open-source model avoids a product subscription, although connected DNS providers may charge separately. Its scope is specialized: teams looking for a hosted DNS console, general-purpose DNS administration, RBAC, or audit logs should choose another tool. ExternalDNS is the stronger fit for Kubernetes-centric automation, while organizations needing broader administrative governance should look elsewhere.

ExternalDNS pros and cons

  • Where it wins
    • Open-source and free to run in self-hosted Linux environments
    • Supports AWS Route 53, Cloudflare, Google Cloud DNS, and other providers
    • Includes filtering, dry runs, ownership registries, webhooks, and metrics
  • Where it doesn't
    • Requires Kubernetes and self-hosted operation
    • DNS provider charges are separate
    • Does not provide RBAC or audit logs

ExternalDNS fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update