How do I install the Dns Cutover skill?

Run npx skillmds@latest add starr-del/dns-cutover in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dns Cutover safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dns Cutover?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dns Cutover free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dns Cutover?

Starr-del (@starr-del) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dns Cutover by starr-del — Agent Skill

Name: Dns Cutover
Author: Starr-del

Dns Cutover

Generate the exact DNS records for pointing a custom domain at Vercel, Netlify, Cloudflare Pages, or GitHub Pages — and validate the user's actual records before they flip the domain. Use whenever the user mentions custom domains, DNS, nameservers, 'domain not working', CNAME/A records, or connecting a purchased domain to a deployed site. Runs fully offline — no API keys, no network, no credentials.

Starr-del Updated Sep 17, 2026

File contents

dns-cutover

Part of shipsafe — offline deploy-safety skills. Every script is stdlib-only Python 3.8+; nothing leaves the machine.

Two modes:

# 1) What records do I need?
python3 scripts/dns_cutover.py plan <domain> <platform>
# 2) Are my records right? (paste zone export or `dig +noall +answer` output into a file)
python3 scripts/dns_cutover.py check <domain> <platform> <records_file> [--json]

Platforms: vercel, netlify, cloudflare-pages, github-pages.

check validates apex and www records, and additionally catches the three classic cutover mistakes:

apex CNAME — illegal on standard DNS, silently breaks MX/email at most registrars
stale extra A records — round-robin traffic to the dead old host (looks like 'site randomly down')
conflicting A + CNAME on the same name

Process to walk the user through: lower TTL to 300s the day BEFORE → run plan → set records → export/dig the records into a file → run check → only then flip. After cutover, verify HTTPS on BOTH apex and www — cert issuance is the step that fails silently.

Some values are project-specific (e.g. <yoursite>.netlify.app); the script marks these and the user's dashboard value wins.

Exit codes: 0 ok, 1 problems found.

All paths below are relative to this skill's directory (dns-cutover/).

Frequently asked questions