External DNS
External DNS automates the synchronization of Kubernetes Services and Ingresses with your DNS provider. By dynamically managing DNS records, it ensures your Kubernetes resources are always discoverable through public DNS servers - eliminating manual updates and reducing human error.
How It Works
External DNS continuously monitors your Kubernetes API for relevant resources (Services, Ingresses, Gateways, or HTTPRoutes). It then translates these resources into the desired DNS records and updates your DNS provider automatically. This works seamlessly with the DNS services of major cloud providers like AWS and Azure, as well as smaller, regional providers such as TransIP in the Netherlands.
Key Benefit
With External DNS, you gain DNS provider-agnostic control - manage your DNS records directly through Kubernetes, without vendor lock-in or manual intervention.
External DNS in the HavenPlus context
External DNS supports a wide range of DNS providers, making it impractical to offer a reference implementation for each one. To simplify setup, we provide:
- A fully configured overlay for Azure DNS, ready to use out of the box.
- A generic overlay template for all other providers.
Use the generic overlay as your starting point, then refer to the official ExternalDNS documentation or DNS provider-specific tutorials to tailor the configuration to your DNS provider.
Further Configuration
The base ExternalDNS configuration includes default properties, which you can override in your provider overlay. For detailed guidance on customizing these settings, see the configuration guide.