skills.rest
wagnerra23
wagnerra23COMMUNITY
Explore all skills by this author →
GitHub

hostinger-dns-autonomy

Enforce API-first Hostinger DNS A record updates with token validation and overwrite protection.

Updated May 14, 2024
Search Tags:#secret management#dns#hostinger#api-first#token validation#incident guardrails#automation policy
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill hostinger-dns-autonomy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hostinger-dns-autonomy
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/hostinger-dns-autonomy
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill hostinger-dns-autonomy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unsafe or inefficient escalation by blocking requests to perform Hostinger DNS changes via the hPanel UI and instead enforcing the documented API/CLI-first procedure using the correct Hostinger DNS API token and guardrails.

Core Features & Use Cases

  • Tier A blocking policy: Stops agents from asking Wagner to edit DNS records through Hostinger UI whenever an API/CLI path exists.
  • Secret-first retrieval (Path 0 memory index): Forces the agent to consult the canonical secret index and only fall back to other known token locations if the index lacks an entry.
  • Token validity handling: Differentiates between inaccessible tokens (Tier 0 gap) and stale/expired tokens (secret rotation), including explicit validation via Hostinger DNS API and safe next actions.
  • Canonical A-record workflow: Provides the production-ready curl recipe that sets DNS records with overwrite protection (overwrite: false) and includes propagation validation steps.

Quick Start

Ask the agent to create the needed Hostinger DNS A record using the documented Hostinger DNS API token without involving hPanel, and let the Skill enforce token lookup, rotation rules, and propagation validation.

Frequently Asked Questions about hostinger-dns-autonomy

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

FAQPage Schema
How do I automate Hostinger DNS A record updates without using hPanel?▼

You can automate Hostinger DNS A record updates by enforcing an API-first workflow that retrieves the API token from a canonical secret index and applies DNS changes via the Hostinger DNS API.

What is the safest way to prevent accidental DNS zone wipes when updating records via the Hostinger API?▼

The safest way to prevent DNS zone wipes is to use the Hostinger DNS API with the overwrite:false parameter, ensuring existing records remain intact while updating specific A records.

How should I handle stale or expired Hostinger DNS API tokens during automation?▼

Handle stale Hostinger DNS API tokens by validating token access first, differentiating between inaccessible tokens requiring a Tier 0 gap report and expired tokens requiring secret rotation.

Do I need to validate my Hostinger DNS API token before attempting to update subdomain records?▼

Yes, you need to validate your Hostinger DNS API token before updating subdomain records by testing access against the API to ensure the token is active and prevent unauthorized changes.

Why does my DNS automation workflow require consulting a secret index before modifying Hostinger records?▼

Your DNS automation workflow requires consulting a canonical secret index first to locate the correct Hostinger DNS API token, preventing unauthorized access and ensuring proper secret rotation.

What should I do if my Hostinger DNS API token is completely inaccessible during an automation task?▼

If your Hostinger DNS API token is inaccessible, you should report a Tier 0 gap and avoid falling back to hPanel UI changes, maintaining the required API-first automation policy.

Related Skills

Explore More Software Engineering Skills→
flavien-iaflavien-ia
34

_dns-hostinger

Update Hostinger domain nameserver records to Cloudflare via the REST API.

Community
Advanced
phyter1phyter1

fleet-dns

Manage Cloudflare DNS records via API for listing, adding, removing, and verifying entries.

Community
Intermediate
iceflowericeflower

secrets-management

Automates secret lifecycle management across Kubernetes, CI/CD pipelines, and multi-cloud environments with rotation and leak detection.

Community
Advanced
julianobarbosajulianobarbosa
7

Azure Integration

Manage Cloudflare DNS records for Azure-hosted applications via REST API.

Community
Advanced