External DNS

DNS automation component for publishing Foundation services.

Agentic Friendly

Component Category

Network / DNS automation

Component Description

ExternalDNS automates the creation and management of DNS records from Kubernetes resources.

Why It Is Used

In BullSequana AI Foundation, ExternalDNS simplifies service publication by keeping DNS records aligned with exposed services and ingress resources. This reduces manual DNS operations and improves consistency across environments.

Learn More

Deployment notes

External DNS deploys into the external-dns namespace at sync wave 4 in the common tier. It writes to the zone of the configured DNS provider: Azure DNS by default, an RFC2136 server or Amazon Route 53. It watches Service, HTTPRoute, and GRPCRoute resources to create DNS records automatically. The sync interval is two minutes, and it only creates and updates records, never deletes them.

The platform leaves External DNS out when no DNS provider is configured, and EXTERNAL_DNS_COMPONENT_ENABLED=false leaves it out with any provider. See DNS and TLS outside Azure.

Interacts With

  • Gateway API, because it watches HTTPRoute and Gateway resources to publish DNS records for exposed endpoints.
  • cert-manager, because both depend on the same routable DNS zones for public endpoint setup and certificate validation.
  • Platform UIs and APIs such as Argo CD, Grafana, Temporal, and PgAdmin, whose hostnames are published through DNS automation.

On this page