Skip to main content

DNS Add-on

The DNS add-on publishes DNS records for your Kubernetes Services and Ingresses automatically into a NetActuate DNS zone you own. When enabled, NetActuate installs and operates a controller that watches your workloads and keeps records in the zone in sync with them, so you annotate a Service or Ingress with a hostname and the record appears without a manual step. It works on both edge and in-VPC clusters.

Enable the add-on​

  1. Navigate to Infrastructure -> Kubernetes and open your cluster.
  2. Open the Managed Add-ons tab.
  3. Enable DNS. Provide:
    • Zone - an existing DNS zone in your NetActuate account that the add-on will manage records in. You must already own the zone under Networking -> Domains.
    • Mode - the record management policy the controller applies (see Policy below).
  4. Confirm. NetActuate installs the controller and moves the add-on to ready when installation or reconciliation completes. If it reports degraded or failed, use Repair on the same tab.

Modes​

The DNS add-on mode field accepts these values:

  • full-zone - the add-on manages records directly in the selected zone.
  • subzone - the add-on manages records in a delegated subzone under the selected zone.

Annotate a Service or Ingress​

Request a record by adding the hostname annotation to a Service or Ingress:

apiVersion: v1
kind: Service
metadata:
  name: web
  annotations:
    external-dns.alpha.kubernetes.io/hostname: web.example.com
spec:
  type: LoadBalancer
  selector:
    app: web
  ports:
    - port: 80
      targetPort: 8080

The hostname must sit within the zone you selected when enabling the add-on. The controller reads the address the Service or Ingress exposes and writes the matching record into the zone.

Supported record types​

The add-on manages these record types: A, AAAA, CNAME, TXT, MX, SRV, SPF, and PTR. Provider-specific aliasing record types are not supported: there is no ALIAS or ANAME. Use a CNAME where you would otherwise reach for an alias.

Policy​

The add-on manages records with a sync policy: it creates and updates records to match your workloads, and it garbage-collects records it created when the workload or its annotation is removed. Records the add-on owns are cleaned up on delete, so a removed Service or Ingress does not leave a stale record behind. The add-on only touches records it manages in the selected zone; records you create by hand in the same zone are left alone.

The add-on state field shows platform installation and reconciliation state only. It does not prove the DNS controller pod is healthy or that every expected record has been published. Check the Kubernetes workload and verify DNS answers when monitoring production records.

  • Domains - create and manage the DNS zone the add-on writes into, and review records the add-on produces

Need Help?​

Contact support@netactuate.com or open a support ticket from the portal.