hetzner-dns

Name: hetzner-dns
Availability: InStock
Author: HybridAI

Manages Hetzner DNS zones and RRsets with guarded record operations.

126|11|Updated Feb 24, 2026

Search Tags:#hetzner #dns #api token #record management #infrastructure automation #rrset #guarded writes

Ready to run

npx skills add https://github.com/HybridAIOne/hybridclaw --skill hetzner-dns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: hetzner-dns
Source: https://github.com/HybridAIOne/hybridclaw/tree/main/skills/hetzner-dns
Command: npx skills add https://github.com/HybridAIOne/hybridclaw --skill hetzner-dns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates discovering Hetzner DNS zones and safely managing DNS record data while preventing accidental or unauthorized changes.

Core Features & Use Cases

Zone and record discovery: Lists zones and retrieves existing RRsets to find record-id values needed for updates and deletes.
Guarded record operations: Creates, updates, adds/removes record values, and deletes records/zones with explicit operator grant for mutations.
Live vs. dry-run control: Supports planning and request payload generation for reviews, and only performs live API calls when the emitted request is executed by the runtime.

Quick Start

Ask the assistant to plan an operation to list your Hetzner DNS zones for inspection before making any changes.

Frequently Asked Questions about hetzner-dns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate Hetzner DNS record management for infrastructure provisioning?▼

You can automate Hetzner DNS record management by using a helper wrapper to generate plan and HTTP-request payloads for A, AAAA, CNAME, and TXT records. The wrapper injects the API token as an Auth-API-Token header without exposing it to the model.

What is the safest way to update TXT records for domain verification on Hetzner DNS?▼

The safest way to update TXT records for domain verification is using guarded write operations that support adding or removing specific record values. This requires explicit operator grant for mutations and allows dry-run payload generation for review before live execution.

How do I find the record ID needed to update or delete an existing Hetzner DNS RRset?▼

To find the record ID for a Hetzner DNS RRset, you list zones and retrieve existing RRsets to inspect the current DNS data. This discovery phase acts as a preflight check to identify the exact record-id values required before performing any updates or deletes.

Can I plan DNS zone changes in Hetzner before executing live API calls?▼

Yes, you can plan DNS zone changes in Hetzner before executing live API calls by generating request payloads for review. The runtime only performs live API mutations when the emitted request is explicitly executed, ensuring safe preflight planning.

Do I need to provide my Hetzner DNS API token directly to the model for record operations?▼

No, you do not provide your Hetzner DNS API token directly to the model. The provided DNS helper wrapper automatically injects the HETZNER_DNS_API_TOKEN as an Auth-API-Token header, ensuring your credentials remain secure and unexposed.

What are the limitations of using guarded writes for Hetzner DNS infrastructure automation?▼

Guarded writes for Hetzner DNS infrastructure automation require tier-gating for read, write, and delete actions, meaning mutations need explicit operator grant. This safety constraint prevents unauthorized changes but requires validation before executing live API requests.