Skip to main content
DNZ speaks the httpreq protocol of lego, which Traefik uses too, so these tools can create the _acme-challenge TXT record in DNZ and remove it afterwards.
For the CA to see the record, DNZ must be the zone’s public nameserver (the zone is delegated to DNZ), or _acme-challenge in public DNS must be a CNAME to a name DNZ serves.

Create a token

Under Settings → API tokens → Create token, give the token records.write, preferably limited to the zones that need certificates. Or:
See API tokens.

Configure your client

The httpreq username can be anything; the token is the password. DNZ creates a TXT record with a TTL of 60 in the matching zone and deletes it on cleanup. See the endpoint reference.

Other ways

  • RFC 2136: certbot’s dns-rfc2136 plugin and lego/Traefik’s rfc2136 provider can use a TSIG key limited to TXT at _acme-challenge.*. See Dynamic updates.
  • dnz-proxy gets certificates itself, with no client to run. See Certificates.
  • DNZ’s own certificate for DoT/DoH can come from lego with this endpoint. See Encrypted DNS.