Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Repair DNS Cache Staleness

    1

    Repair ignored DNS TTLs, startup-only resolution, stale endpoint reuse, retry-to-same-address loops, discovery refresh stampedes, and DNS/pool confusion.

    $8.99

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    Security scanned
    Repair DNS Cache Staleness

    Repair DNS Cache Staleness

    Example session with this skill installed

    Our Go service calls an internal API by hostname. We added a custom DNS cache six months ago; it resolves once and keeps the IP until process restart. After blue/green deploys the old backend is removed, but long-lived processes continue dialing the retired IP and fail until restarted. The HTTP transport also keeps idle connections, so we need to distinguish DNS staleness from pooled connections. Repair locally with a fake resolver and two local HTTP endpoints. Use the DNS TTL supplied by the test fixture; do not query production DNS, change real TTLs, disable caching, or blindly retry POST requests.

    • Read your context and instructions
    • Compiled the repair dns cache

    DNS cache staleness found. The application resolves once and retains the address until restart, while HTTP connection reuse is a separate lifecycle. The repair honors the supplied TTL, coalesces refresh, rotates address generations, separates DNS from pooling, and adds deterministic A-to-B endpoint tests. Production DNS and resolver behavior remain unverified.

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

    What you get

    Eliminate stale IP pinning after service failovers or rollouts.Implement TTL-aware caching for custom service discovery wrappers.Prevent DNS storms using refresh coalescing and single-flight logic.Verify address rotation in CI with fake clocks and local endpoints.

    About this skill

    DNS and service-discovery failures are often application lifecycle bugs: a custom resolver caches one IP forever, failed endpoints stay selectable, retries repeatedly choose the same dead address, or every caller triggers an emergency refresh at once.

    Repair DNS Cache Staleness gives an AI coding agent a repository workflow for tracing resolution ownership, TTL/expiry behavior, address generations, connection-pool interaction, failed-address handling, refresh coalescing, and retry safety. It proves address rotation with fake clocks and local endpoints.

    It does not query or change production DNS, flush live caches, disable caching globally, or invent TTL values.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 1 month ago

    • Passed all security checks, Safe to install

    Listed1 month ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions