Automate PowerDNS Authoritative HTTP
HumDay reads PowerDNS Authoritative HTTP’s own published API description and derives 32 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What HumDay can do in PowerDNS Authoritative HTTP
17 documented operations change something in PowerDNS Authoritative HTTP.
- POSTCreates a new domain, returns the Zone on creation.
/servers/{server_id}/zones - PATCHCreates/modifies/deletes RRsets present in the payload and their comments.
/servers/{server_id}/zones/{zone_id} - POSTAdd a TSIG key
/servers/{server_id}/tsigkeys - PUTSend a DNS NOTIFY to all slaves.
/servers/{server_id}/zones/{zone_id}/notify - POSTCreates a set of metadata entries
/servers/{server_id}/zones/{zone_id}/metadata - POSTCreates a Cryptokey
/servers/{server_id}/zones/{zone_id}/cryptokeys - PUTFlush a cache-entry by name
/servers/{server_id}/cache/flush - DELETEDeletes this zone, all attached metadata and rrsets.
/servers/{server_id}/zones/{zone_id} - PUTModifies basic zone data.
/servers/{server_id}/zones/{zone_id} - DELETEDelete the TSIGKey with tsigkeyid
/servers/{server_id}/tsigkeys/{tsigkey_id} - PUTThe TSIGKey at tsigkeyid can be changed in multiple ways: Changing the Name, this will remove the key with tsigkeyid after adding.
/servers/{server_id}/tsigkeys/{tsigkey_id} - DELETEDelete all items of a single kind of domain metadata.
/servers/{server_id}/zones/{zone_id}/metadata/{metadata_kind} - PUTRectify the zone data.
/servers/{server_id}/zones/{zone_id}/rectify - PUTRetrieve slave zone from its master.
/servers/{server_id}/zones/{zone_id}/axfr-retrieve - PUTReplace the content of a single kind of domain metadata.
/servers/{server_id}/zones/{zone_id}/metadata/{metadata_kind} - DELETEThis method deletes a key specified by cryptokeyid.
/servers/{server_id}/zones/{zone_id}/cryptokeys/{cryptokey_id} - PUTThis method (de)activates a key from zonename specified by cryptokeyid
/servers/{server_id}/zones/{zone_id}/cryptokeys/{cryptokey_id}
What HumDay can read from PowerDNS Authoritative HTTP
These are the operations a schedule or a trigger can watch.
- GETList all servers
/servers - GETList a server
/servers/{server_id} - GETList all Zones in a server
/servers/{server_id}/zones - GETQuery statistics.
/servers/{server_id}/statistics - GETSearch the data inside PowerDNS
/servers/{server_id}/search-data - GETReturns all ConfigSettings for a single server
/servers/{server_id}/config - GETGet all TSIGKeys on the server, except the actual key
/servers/{server_id}/tsigkeys - GETzone managed by a server
/servers/{server_id}/zones/{zone_id} - GETGet a specific TSIGKeys on the server, including the actual key
/servers/{server_id}/tsigkeys/{tsigkey_id} - GETReturns a specific ConfigSetting for a single server
/servers/{server_id}/config/{config_setting_name} - GETReturns the zone in AXFR format.
/servers/{server_id}/zones/{zone_id}/export - GETGet all the Metadata associated with the zone.
/servers/{server_id}/zones/{zone_id}/metadata - GETGet all CryptoKeys for a zone, except the privatekey
/servers/{server_id}/zones/{zone_id}/cryptokeys - GETGet the content of a single kind of domain metadata as a Metadata object.
/servers/{server_id}/zones/{zone_id}/metadata/{metadata_kind} - GETReturns all data about the CryptoKey, including the privatekey.
/servers/{server_id}/zones/{zone_id}/cryptokeys/{cryptokey_id}
How automating PowerDNS Authoritative HTTP works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live PowerDNS Authoritative HTTP account.
- Grant access, then go live. You approve the specific PowerDNS Authoritative HTTP operations it may use — and only those.
Automate PowerDNS Authoritative HTTP with these
- OData for namespace microsoft.graph11412 operations
- GitHub811 operations
- Atlassian The Jira Cloud platform474 operations
- Gitlab358 operations
- JIRA 7.6.1324 operations
- Appcenter App Center Client323 operations
- Gitea .321 operations
- Bitbucket292 operations
- Keycloak Admin281 operations
- Apple App Store Connect251 operations
- Files.com222 operations
- Vmware vRealize Network Insight Reference161 operations
Categories
Questions about PowerDNS Authoritative HTTP automation
- Can HumDay connect to PowerDNS Authoritative HTTP?
- Yes. HumDay reads PowerDNS Authoritative HTTP's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 32 operations are documented.
- Do I need to write code to automate PowerDNS Authoritative HTTP?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your PowerDNS Authoritative HTTP account.
- What can HumDay do in PowerDNS Authoritative HTTP?
- 17 of the 32 documented operations change something in PowerDNS Authoritative HTTP, and 15 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my PowerDNS Authoritative HTTP account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to PowerDNS Authoritative HTTP is held behind that approval.
Where this came from
The operations above are read from a published API description for PowerDNS Authoritative HTTP at raw.githubusercontent.com/PowerDNS/pdns/master/docs/http-api/swagger/authoritative-api-swa. Descriptions are the provider’s own words, not ours. Last published 2021-01-18.