# ExternalDNS

ExternalDNS is a self-hosted network services app. ExternalDNS synchronizes exposed Kubernetes Services and Ingresses with DNS providers. It is open source and self-hosted, installable on Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/4642/externaldns

## Description

ExternalDNS synchronizes exposed Kubernetes Services and Ingresses with DNS providers.

## Platform availability

Available on 1 of 9 platforms: Helm.

## Health score

73/100 (Good), based on 3 of 4 factors.
- Maintained: 100 (last commit 7 days ago)
- Popular: 79 (9,104 GitHub stars)
- Easy to install: 10 (1 install platform)

## Links

- Documentation: https://kubernetes-sigs.github.io/external-dns/
- Kubernetes (Helm): https://artifacthub.io/packages/helm/external-dns/external-dns
- GitHub: https://github.com/kubernetes-sigs/external-dns

## Common questions

### Does ExternalDNS require Kubernetes to use a particular DNS provider?

No. ExternalDNS controls DNS records dynamically through Kubernetes resources in a DNS provider-agnostic way.

### What problem can occur when internal domain names are resolved through external DNS?

Mixing internal and external DNS can cause Active Directory clients to get stuck on external DNS and lead to resolution glitches.

### What basic redundancy setup is suggested for self-hosted DNS?

Use at least two DNS VMs on different subnets, not the same IP ranges. Hosting them in separate cloud providers can further reduce risk.

### Does the ExternalDNS website point directly to a fixed docs version?

The ExternalDNS website redirects to the latest documentation.

---
Source: Our Local Host (https://ourlocalhost.com/app/4642/externaldns), the self-hosted and open-source app directory.
