Skip to main content

The UI cannot connect to PowerDNS

Check that PDNS_API_URL is reachable from the machine or container running PowerDNS Web UI. From that environment:
If this fails, fix networking, the PowerDNS webserver configuration, or the API key before debugging the UI.

401 or unauthorized responses

The value of PDNS_API_KEY must match api-key in pdns.conf. Restart PowerDNS after changing pdns.conf.

404 for server or zones

Check PDNS_SERVER_ID. Most installations use:
If your API exposes a different server ID, use that value.

Docker cannot reach PowerDNS on localhost

Inside a container, localhost means the container itself. Use a reachable host instead, such as:
for another Compose service, or a host bridge address when PowerDNS runs on the Docker host.

ALIAS records do not resolve

Confirm that PowerDNS is configured for ALIAS expansion:
The resolver must not point back to the authoritative server itself.

Slave zone transfer fails

Check the primary zone metadata and network path:
  • ALLOW-AXFR-FROM includes the secondary server
  • The primary accepts TCP/53 from the secondary
  • The zone master address is correct
  • Firewalls allow the transfer