designate

PowerDNS

Pre-requisites

You have to install a PowerDNS server first, this is outside the scope of this document. You can review instructions on how to prepare the PowerDNS server through the Designate documentation.

Configuration

You will need to configure your PowerDNS server to allow the Designate API to talk to it. This is done by adding the following to your PowerDNS configuration into your inventory file.

In this example, PowerDNS will be configured to validate if the DNS changes have been propagated to all DNS servers by hitting the PowerDNS backend. It will use the virtual IP address of the cloud to request AXFRs.

In this example, it's assumed that the PowerDNS server is running at 192.168.1.10 and reachable by the Kubernetes cluster using secret123 as the token.

!!! note

You will need to make sure you configure your Glue DNS records with your
registrar to point towards your PowerDNS instances (also frequently called
"registering nameservers").  This is out of the scope of this document.

designate_pools:
  - name: default
    description: Default PowerDNS Pool

    ns_records:
      - hostname: ns1.example.com.
        priority: 1
      - hostname: ns2.example.com.
        priority: 2

    nameservers:
      - host: 192.168.1.10
        port: 53

    targets:
      - type: pdns4
        description: PowerDNS4 DNS Server
        masters:
          - host: "{{ keepalived_vip }}"
            port: 5354
        options:
          host: 192.168.1.10
          port: 53
          api_endpoint: http://192.168.1.10:8081
          api_token: secret123