# External DNS (/docs/runtime/components/external-dns)



Component Category [#component-category]

Network / DNS automation

Component Description [#component-description]

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

Why It Is Used [#why-it-is-used]

In BullSequana AI Runtime, 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 [#learn-more]

* [ExternalDNS documentation](https://kubernetes-sigs.github.io/external-dns/latest/)
* [kubernetes-sigs/external-dns on GitHub](https://github.com/kubernetes-sigs/external-dns)

Deployment notes [#deployment-notes]

External DNS deploys into the `external-dns` namespace at sync wave 5 in the common tier. It is configured with the Azure DNS provider and watches `Service`, `HTTPRoute`, and `GRPCRoute` resources to create DNS records automatically. The sync interval is two minutes.

Interacts With [#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.