Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    DNS Zone Validator

    1

    Validate BIND DNS zone files for syntax errors, RFC violations, and serial number hygiene.

    $2.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    DNS Zone Validator

    DNS Zone Validator

    Example session with this skill installed

    Check db.internal.lan for errors. It's a private zone. I've also provided db.internal.lan.old to verify the serial was updated.

    • Read your context and instructions
    • Compiled the dns zone validator

    I have analyzed db.internal.lan using the DNS Zone Validator. I compared it against the previous version to verify serial increments and performed a hygiene audit.

    DNS Validation Report: db.internal.lan

    Check TypeResultDetails
    BIND SyntaxPASSEDnamed-checkzone returned code 0.
    SOA SerialFAILEDSerial 2023101001 is identical to the previous version.
    NS CountWARNINGOnly 1 NS record found (ns1.internal.lan). Minimum 2 recommended.
    RFC 2181PASSEDNo CNAME collisions or invalid MX/NS targets detected.
    Glue RecordsPASSEDAll in-zone nameservers have corresponding A/AAAA records.
    IP ExposureINFOPrivate IP range detected (10.0.0.0/8). Flagged as safe for private zone.
    SOA TimersPASSEDRefresh (3600), Retry (600), and Expire (86400) are within normal ranges.

    Issues Found:

    • The SOA serial was not incremented. BIND will not propagate these changes to secondary servers.
    • Redundancy risk: Only one nameserver is defined. If ns1 fails, the zone becomes unreachable.

    Next steps

    1. Run with --bump-serial to automatically increment the SOA serial to 2023101002.
    2. Add a second NS record and a corresponding A record for ns2.internal.lan.
    3. Reload the BIND service after the serial is corrected.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    DNS zone file errors often stay hidden until a reload fails or propagation breaks. This skill validates and lints BIND zone files to ensure they meet both RFC standards and operational best practices before they reach your nameservers.

    What it does

    • Syntax validation runs the official named-checkzone utility to catch parser errors.
    • RFC compliance flags forbidden configurations like CNAMEs coexisting with other records or CNAMEs as MX targets.
    • Serial management detects un-bumped SOA serials and enforces YYYYMMDDnn formatting.
    • Infrastructure hygiene identifies missing glue records, low TTLs, and insufficient NS records.
    • Security checks warns when private IP addresses (RFC 1918) are detected in public-facing zones.

    How it works

    1. Analyze the target zone file using named-checkzone for baseline syntax correctness.
    2. Scan for hygiene issues like improper SOA timers or duplicate records.
    3. Compare against a previous version of the file to verify serial number increments.
    4. Update the zone file automatically with a bumped serial number if requested.

    Frameworks & tools

    The skill relies on bind9-utils (specifically named-checkzone) for authoritative syntax checks. The hygiene and linting logic is implemented in Python.

    Why this beats prompting it yourself

    Generic LLM prompts often miss subtle DNS RFC requirements like the prohibition of CNAMEs on the zone apex. This skill combines the industry-standard BIND toolchain with programmatic logic to catch edge cases that manual review or simple pattern matching will miss.

    Use cases

    • Validating zone files before a BIND server reload.
    • Migrating DNS records between different providers or servers.
    • Automating serial number updates during CI/CD deployments.
    • Auditing public DNS zones for accidental private IP leakage.

    Known limitations

    Requires named-checkzone to be installed on the host for full syntax validation. Hygiene checks operate independently but cannot replace the official BIND parser.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.

    Requires bind9-utils or bind-utils for authoritative syntax checking. Works specifically with BIND-style zone file formats.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    Permissions

    Terminal / Shell
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    The skill uses the official `named-checkzone` utility from the BIND toolchain to ensure 100% parity with how actual nameservers parse your files, catching errors that generic AI prompts often miss.

    It supports all standard BIND-format zone files, including those with A, AAAA, CNAME, MX, TXT, SRV, and SOA records, while enforcing RFC-compliant logic for each.

    Yes, the skill can be configured to compare your current file against a previous version and automatically increment the SOA serial number (using YYYYMMDDnn format) if changes are detected.

    The skill requires `bind9-utils` to be installed on the environment where the agent is running to perform the authoritative syntax validation.

    Beyond syntax, the skill checks for "hygiene" issues like missing glue records, private IP leakage in public zones, and RFC violations such as CNAMEs at the zone apex.

    New in DevOps & Cloud