PowerDNS Authoritative HTTP API

Name: PowerDNS Authoritative HTTP API
Brand: PowerDNS Authoritative HTTP API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureNetworkingapiKey36 EndpointsREST

For Agents

Install Jentic One Beta

Connect the PowerDNS Authoritative HTTP API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PowerDNS Authoritative HTTP API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with PowerDNS Authoritative HTTP API.

Create, modify, and delete DNS zones with full record set management via zone patching

Manage DNSSEC cryptographic keys including generation, activation, and deletion per zone

Configure TSIG keys for authenticated zone transfers between primary and secondary servers

GET STARTED

Start building with PowerDNS Authoritative HTTP API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use PowerDNS Authoritative HTTP API for, with concrete tasks.

★ DNS Zone and Record Management

Programmatically manage DNS zones and their record sets on PowerDNS authoritative servers. The API supports creating zones in Native, Master, or Slave mode, patching individual record sets (add, modify, delete), and exporting full zone data. Record changes are applied atomically per zone patch request, ensuring consistency. Supports all standard record types including A, AAAA, CNAME, MX, TXT, SRV, and NS.

Create a new zone 'example.com' in Native mode via POST /servers/{server_id}/zones, then patch it to add an A record pointing to 192.0.2.1

DNSSEC Key Management

Manage DNSSEC cryptographic keys for zones to enable authenticated DNS responses. The API provides endpoints to list, create, activate, deactivate, and delete cryptographic keys per zone. Key rollovers can be automated by creating new keys, activating them, and deactivating old keys in sequence. Supports both KSK and ZSK key types with configurable algorithms.

List all cryptographic keys for zone 'example.com' via GET /servers/{server_id}/zones/{zone_id}/cryptokeys and identify which key is currently active

DNS Infrastructure Automation

Automate DNS infrastructure operations including cache flushing, zone notifications, AXFR retrieval, and server configuration inspection. The API enables infrastructure-as-code workflows where DNS state is managed declaratively. Cache flush endpoints allow targeted invalidation after record changes, while notify triggers immediate propagation to secondary servers without waiting for SOA timers.

Flush the cache for 'example.com' using PUT /servers/{server_id}/cache/flush, then trigger a NOTIFY to secondaries via PUT /servers/{server_id}/zones/{zone_id}/notify

AI Agent DNS Operations

Enable AI agents to manage DNS infrastructure through Jentic by discovering zone and record management operations via intent search. Agents can create zones, update records, manage DNSSEC keys, and monitor server state without memorizing the PowerDNS API structure. Jentic provides operation schemas with field requirements so agents construct valid zone patches on first attempt.

Search Jentic for 'add a DNS A record', load the PowerDNS zone patch schema, and execute to add an A record for 'www.example.com' pointing to a specified IP address

Key Endpoints

36 endpoints — the powerdns authoritative http api provides programmatic control over powerdns authoritative nameserver instances.

METHOD

PATH

DESCRIPTION

GET

/servers/{server_id}/zones

List all zones on the server

POST

/servers/{server_id}/zones

Create a new DNS zone

PATCH

/servers/{server_id}/zones/{zone_id}

Update records in a zone (add/modify/delete)

GET

/servers/{server_id}/zones/{zone_id}/cryptokeys

List DNSSEC cryptographic keys for a zone

PUT

/servers/{server_id}/cache/flush

Flush the server cache for a domain

GET

/servers/{server_id}/zones/{zone_id}/export

Export zone data in AXFR format

PUT

/servers/{server_id}/zones/{zone_id}/notify

Trigger NOTIFY to secondary servers

GET

/servers/{server_id}/search-data

Search records across all zones

GET

/servers/{server_id}/zones

List all zones on the server

POST

/servers/{server_id}/zones

Create a new DNS zone

PATCH

/servers/{server_id}/zones/{zone_id}

Update records in a zone (add/modify/delete)

GET

/servers/{server_id}/zones/{zone_id}/cryptokeys

List DNSSEC cryptographic keys for a zone

PUT

/servers/{server_id}/cache/flush

Flush the server cache for a domain

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

PowerDNS X-API-Key credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens and never see the raw API key directly.

Intent-based discovery

Agents search by intent (e.g., 'create a DNS zone') and Jentic returns matching PowerDNS operations with their input schemas, so the agent can manage zones and records without reading API documentation.

Time to first call

Direct PowerDNS integration: 2-3 days for understanding zone patching format and DNSSEC workflow. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using PowerDNS Authoritative HTTP API through Jentic.

What authentication does the PowerDNS Authoritative HTTP API use?

The PowerDNS API uses an API key passed in the X-API-Key HTTP header. This key is configured in the PowerDNS server's pdns.conf file via the api-key setting. Through Jentic, this key is stored encrypted in the credential vault and injected automatically into requests.

Can I manage individual DNS records with the PowerDNS API?

Yes. Use PATCH /servers/{server_id}/zones/{zone_id} with a JSON body containing rrsets to add, modify, or delete individual record sets. Each rrset specifies the record name, type, TTL, and changetype (REPLACE or DELETE). Multiple record changes can be applied atomically in a single request.

What are the rate limits for the PowerDNS Authoritative HTTP API?

The PowerDNS API is self-hosted, so rate limits depend on your server configuration and hardware capacity. There are no vendor-imposed external rate limits. Performance depends on zone count, record volume, and server resources allocated to the web API listener.

How do I create a DNS zone through the PowerDNS API using Jentic?

Install the SDK with pip install jentic, then search for 'create a DNS zone'. Jentic returns the POST /servers/{server_id}/zones operation schema requiring name, kind (Native/Master/Slave), and nameservers array. Execute to create the zone, then use PATCH to add records.

Does the PowerDNS API support DNSSEC key management?

Yes. The /servers/{server_id}/zones/{zone_id}/cryptokeys endpoints let you list, create, activate, deactivate, and delete DNSSEC keys. You can automate key rollovers by creating new keys with POST, activating them with PUT, and deleting old keys with DELETE. The rectify endpoint ensures zone data consistency after key changes.

PowerDNS Authoritative HTTP API

Connect the PowerDNS Authoritative HTTP API to your agent

Capabilities

Start building with PowerDNS Authoritative HTTP API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs