Skip to content
Back to skills

Domain Dns Ops

ASecurity

DNS/domain ops: registrars, Cloudflare zones, redirects, DNS/HTTP verification.

  • 10 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 10, 2026
ai-agentsgobashrailsdebugginggitapi

Works with

  • cli
  • api

Security analysis

A96/100
  • mediumUses curl or wget to download content

Pro shows the line behind each finding and how to fix it

Scanned October 10, 2026

npx -y skills add mouadja02/skills --skill domain-dns-ops --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Domain Dns Ops?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Domain Dns Ops
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mouadja02-domain-dns-ops/badge)](https://www.skillsdirectory.com/skills/mouadja02-domain-dns-ops)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: domain-dns-ops
description: "DNS/domain ops: registrars, Cloudflare zones, redirects, DNS/HTTP verification."
source: "https://github.com/steipete/agent-scripts"
attribution: "steipete/agent-scripts by Peter Steinberger"
version: "1.0.0"
---

# Domain/DNS Ops

> **Attribution:** Sourced from [steipete/agent-scripts](https://github.com/steipete/agent-scripts) by [Peter Steinberger](https://github.com/steipete).

## When to Use

- Setting up DNS zones and records on Cloudflare
- Configuring vanity domains, redirects, and nameserver delegation
- Verifying DNS propagation and HTTP redirect chains

## Golden Path (new vanity domain → Cloudflare → redirect)

1. **Decide routing model**
   - Page Rule redirect (small scale, per-zone).
   - Bulk Redirects (account-level).
   - Worker route (fallback).

2. **Cloudflare zone**
   - Create zone in Cloudflare dashboard, then confirm:
     ```bash
     curl -s "https://api.cloudflare.com/client/v4/zones?name=example.com" \
       -H "Authorization: Bearer $CLOUDFLARE_API_TOKEN" | jq '.result[0] | {id, name, status}'
     ```

3. **Nameservers**
   - Update nameservers at your registrar to Cloudflare's NS records.

4. **DNS placeholders (so CF can terminate HTTPS)**
   - Proxied apex `A` → `192.0.2.1` (placeholder)
   - Proxied wildcard `A` → `192.0.2.1`

5. **Redirect setup**
   - Page Rule: destination URL + `301` permanent redirect.
   - Or use Cloudflare Bulk Redirects for multiple domains.

6. **Verify**

```bash
# DNS check
dig +short example.com @1.1.1.1

# HTTPS redirect
curl -I https://example.com
# Expect: HTTP/2 301 or 302 with Location header
```

## Common Commands

```bash
# Check if domain resolves to Cloudflare
dig +short example.com @1.1.1.1

# Check HTTP/HTTPS redirect
curl -sIL https://example.com | grep -E "HTTP/|Location:"

# Check DNS propagation
dig +short example.com @8.8.8.8
dig +short example.com @1.1.1.1
```

## Guardrails

- Confirm registrar before debugging Cloudflare "invalid nameservers" (often "wrong registrar").
- Prefer reversible steps; verify after each change (NS → DNS → redirect).
- Do not print API tokens or secrets.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…