Skip to content
Agentmart
Submit a tool

custom-domain-email-dns-diagnosis

Skill by ever-just

IndexedMIT★ 5
Write a review

Chalk Labs

Need help deploying custom-domain-email-dns-diagnosis?

Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.

Book a call

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/ever-just-custom-domain-email-dns-diagnosis

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

The publisher has not written a description yet.

Use cases: productivity

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions: not checked yet.

What's inside

Skill name
custom-domain-email-dns-diagnosis
Description
None
License
MIT
Instructions
75 lines in SKILL.md · view on GitHub

Agent Skills spec issues

  • invalid YAML frontmatter: Nested mappings are not allowed in compact mappings at line 2, column 14:
  • name: missing
  • description: missing

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Custom-Domain Email / DNS Diagnosis — Agent Skill

Figure out **who actually controls a custom domain's DNS**, why an email setup is failing, and how to architect email correctly for the infra that exists — then either do it or give an honest limitation. The heart of this skill is the **registrar-vs-DNS-host split**: the failure mode where a domain is registered one place but its DNS is served somewhere else, so the registrar's API can't write records at all.

The neighbors cover adjacent mechanics: [[domain-email-enumeration]] READS an existing setup for OSINT; [[godaddy-api]] WRITES records once GoDaddy is authoritative; [[email-mastery]] writes copy. None of them does the diagnosis this skill owns.

## When to use this skill

- Setting up email on a custom domain and records 'won't save' / the registrar API errors.
- A registrar DNS API returns **'no zone'** / 'domain not found' for a domain you know is registered there.
- Deciding HOW to give a domain email (mailboxes vs forwarding vs Workspace) given the platform in use.
- A user asks for an email setup the infra can't support and you need to explain the constraint honestly.

**Do NOT use this skill for**:
- **Fingerprinting an existing provider** for OSINT → [[domain-email-enumeration]].
- **GoDaddy record-write syntax** once GoDaddy IS the authoritative DNS host → [[godaddy-api]].
- **Writing email copy** → [[email-mastery]].

## Core insight 1 — registrar != DNS host (check nameservers FIRST)

A domain has TWO independent roles: the **registrar** (who you bought/renew it from) and the **DNS host** (whose nameservers actually answer for the zone). They are often the SAME, but not always: a domain **registered at GoDaddy** can have its **nameservers delegated to Vercel** (or Netlify/Cloudflare/Route 53). When that's the case, **GoDaddy is not authoritative**, so the **GoDaddy DNS record API returns 'no zone'** and cannot write records — the zone lives at Vercel. So before assuming the registrar's API can manage DNS, **check where the nameservers point**:

```bash
dig +short NS example.com          # who is AUTHORITATIVE (the DNS host)
whois example.com | grep -i 'registrar:'   # who is the REGISTRAR (may differ)
```
If `dig NS` returns `ns1.vercel-dns.com` (etc.) but the registrar is GoDaddy, you MUST write DNS records at **Vercel**, not GoDaddy — and a GoDaddy-API 'no zone' error is EXPECTED, not a bug. Manage DNS at whoever `dig NS` names; use the registrar only to change registration or re-delegate nameservers.

## Core insight 2 — email records can't break the live site

Email records — **MX**, and **TXT** for SPF/DKIM/DMARC — live in a **different namespace** than the **A/CNAME** records that serve the website. Adding MX/TXT does **not** touch the A/CNAME, so **adding email DNS cannot take the site down**. Reassure accordingly: you can add SPF/DKIM/DMARC/MX to a domain with a live site with zero risk to the site, as long as you ADD records (not replace the whole zone — see Pitfalls).

- **MX** → where mail is delivered (e.g. Google Workspace, native platform, a forwarder).
- **SPF** (`TXT @ v=spf1 include:... ~all`) → who may send as the domain.
- **DKIM** (`TXT selector._domainkey ...`) → signing key from the mail provider.
- **DMARC** (`TXT _dmarc v=DMARC1; p=...`) → policy + reporting.

## Core insight 3 — match architecture to infra

Pick the email approach the available infra actually supports:

| Situation | Fit |
|---|---|
| Platform offers native mailboxes (some hosts/registrars) | Use native mailboxes — simplest, one place. |
| Just need to RECEIVE at the domain, forward to an existing inbox | Domain forwarding → Gmail (MX to the forwarder; no new mailbox). Cheap, but SENDING as the domain still needs SPF/DKIM set up at the sending service. |
| Need real mailboxes + sending + calendar | Google Workspace (or M365): set MX + SPF + DKIM + DMARC at the DNS host. |

## Core insight 4 — honest 'you can't do X without Y'

If the infra can't support what's asked, say so plainly rather than leaving a half-working setup. Examples: 'You can't send as name@domain from Gmail without adding this domain to a sending service and publishing its SPF/DKIM'; 'GoDaddy's API can't write these records because your nameservers are Vercel's — set them at Vercel, or move the nameservers back to GoDaddy first.' A clear limitation beats a broken partial config.

## Recipe — diagnose then act

1. **Locate control**: `dig +short NS domain` (DNS host) and `whois` (registrar). If they differ, DNS is written at the DNS host.
2. **Read current mail state**: `dig +short MX domain`, `dig +short TXT domain`, `dig +short TXT _dmarc.domain` (fingerprint per [[domain-email-enumeration]] if useful).
3. **Explain the split** if registrar != DNS host, and where records must go.
4. **Choose architecture** (Core insight 3) for the goal + infra.
5. **Write records at the DNS HOST** (ADD MX/TXT — safe for the site). If that host is GoDaddy, [[godaddy-api]] has the syntax; if Vercel/Cloudflare/etc., use that host's DNS.
6. **Verify** with `dig` after propagation; for sending, validate SPF/DKIM/DMARC align.
7. **Or state the limitation** honestly if the goal isn't reachable with current infra.

## Pitfalls

1. **Assuming the registrar controls DNS.** Always `dig NS` first. A registrar API 'no zone' error usually means the nameservers are delegated elsewhere — that's the diagnosis, not a failure to retry.
2. **Fearing email records will break the site.** MX/TXT are independent of A/CNAME; adding them can't take the site down. (But do ADD — a PUT that REPLACES the whole zone can drop the A/CNAME; see [[godaddy-api]] on PUT-replaces-zone.)
3. **Setting SPF/MX but forgetting DKIM/DMARC.** Receiving works with just MX; SENDING as the domain (deliverability) needs SPF + DKIM aligned and a DMARC policy.
4. **Multiple SPF TXT records.** A domain may have only ONE `v=spf1` record — merge includes, don't add a second.
5. **Leaving a broken half-setup.** If you can't complete it (infra gap, delegated NS you don't control), say what's needed instead of shipping something that silently doesn't work.
6. **Changing nameservers when you only meant to add email.** You don't need to move NS to add email at the current DNS host — only re-delegate if you deliberately want to move DNS control.

## Combining with other skills
- [[domain-email-enumeration]] — fingerprint the existing provider from MX/SPF/DKIM/DMARC before changing anything.
- [[godaddy-api]] — the record-write syntax once GoDaddy IS the authoritative DNS host (PATCH-adds vs PUT-replaces-zone, nameserver switch, 2FA-blocks-NS-change).

From ever-just/agentskills, MIT.

Signals

Stars
5
Forks
1
Open issues
0
Last commit (this folder)
Jul 12, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Done for you

Rather not set it up yourself?

Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.

See how we build AI agents →Read the case studies

Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.

launches shipped
50+
launches shipped
media placements
500+
media placements
founders on every account
2
founders on every account

Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block

Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.

Get custom-domain-email-dns-diagnosis running in your business

Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.

Goes to the Chalk Labs founders, not the newsletter. Privacy

Need help deploying custom-domain-email-dns-diagnosis?

CallGet help
Cite this page

custom-domain-email-dns-diagnosis skill. Agent Mart. https://agentmart.dev/skills/ever-just-custom-domain-email-dns-diagnosis (last updated 2026-10-24)