home / skills / ominou5 / funnel-architect-plugin / dns-management

dns-management skill

safe

This skill guides you through DNS configuration for custom funnel domains, covering A/CNAME records, SSL setup, redirects, and provider-specific nuances.

npx playbooks add skill ominou5/funnel-architect-plugin --skill dns-management

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.6 KB

---
name: dns-management
description: >
  Guides users through DNS configuration for custom funnel domains.
  Covers A/CNAME records, SSL setup, and platform-specific DNS requirements.
---

# DNS Management

## Common DNS Setup Patterns

### Netlify
```
Type: CNAME
Name: @ (or www)
Value: [site-name].netlify.app
TTL: Auto
```

### Vercel
```
Type: A
Name: @
Value: 76.76.21.21

Type: CNAME
Name: www
Value: cname.vercel-dns.com
TTL: Auto
```

### Cloudflare Pages
```
Type: CNAME
Name: @
Value: [project-name].pages.dev
TTL: Auto
```

## DNS Providers Quick Reference

| Provider | Dashboard URL | Propagation |
|---|---|---|
| Cloudflare | dash.cloudflare.com | Instant (proxied) |
| Namecheap | ap.www.namecheap.com | 1–24 hours |
| GoDaddy | dcc.godaddy.com | 1–24 hours |
| Google Domains | domains.google.com | 1–48 hours |
| Route 53 (AWS) | console.aws.amazon.com/route53 | 1–24 hours |

## SSL/TLS
- **Netlify**: Automatic Let's Encrypt (free)
- **Vercel**: Automatic (free)
- **Cloudflare**: Universal SSL (free, edge-only) or Full SSL (end-to-end)

## www vs non-www
Pick one and redirect the other:
- Set primary domain (e.g., `example.com`)
- Add redirect: `www.example.com → example.com` (301)
- Configure in hosting platform's redirect settings

## Verification
```bash
# Check DNS propagation
dig example.com +short

# Check if SSL is active
curl -I https://example.com

# Check redirect
curl -I http://www.example.com
```

## Troubleshooting
- **DNS not propagating**: Wait 24–48 hours, or flush local DNS cache
- **SSL not working**: Ensure DNS points to hosting provider, not old server
- **Mixed content**: Update all internal links to use `https://`

Overview

This skill guides users through DNS configuration for custom funnel domains, covering A and CNAME records, SSL setup, and platform-specific DNS requirements. It focuses on practical steps to connect domains to hosting platforms like Netlify, Vercel, and Cloudflare Pages, plus verification and common troubleshooting. The goal is to get a funnel live with secure HTTPS and correct redirects quickly.

How this skill works

The skill inspects your target platform and recommends the exact DNS records (A or CNAME), hostnames (root or www), and values to add at your domain registrar. It also outlines SSL/TLS behavior per platform and the recommended redirect strategy between www and non-www. Finally, it provides verification commands and basic troubleshooting steps for propagation, SSL, and mixed-content issues.

When to use it

When pointing a custom domain to a funnel hosted on Netlify, Vercel, or Cloudflare Pages
When switching hosting providers and needing to update DNS records
When HTTPS is missing or SSL certificates are not issuing
When you need to configure or enforce www vs non-www redirects
When verifying DNS propagation and debugging domain connection problems

Best practices

Choose a single canonical domain (www or root) and set a 301 redirect from the other
Use CNAME for subdomains (www) and A records for root domains when required by the platform
Verify DNS changes with dig and curl to confirm propagation and SSL status
Allow up to 48 hours for full propagation but start troubleshooting after 1–2 hours if stuck
Keep hosting provider DNS values current in your registrar and remove old records to avoid conflicts

Example use cases

Connect example.com to Netlify: add a CNAME pointing to [site-name].netlify.app for www or platform-recommended records
Host root domain on Vercel: set an A record to 76.76.21.21 and a CNAME for www to cname.vercel-dns.com
Deploy Cloudflare Pages: add a CNAME for the root or subdomain pointing to [project-name].pages.dev and enable Universal SSL
Fix SSL issuance: ensure DNS points to the current host and clear any conflicting records, then reissue the certificate
Confirm redirects and HTTPS: use curl -I to check that http://www redirects to https://example.com and that SSL headers are present

FAQ

How long until my domain points to the funnel?

Propagation typically completes in 1–24 hours for most registrars, but allow up to 48 hours. Cloudflare proxied records can appear instant.

Why is my SSL not issuing after DNS update?

Common causes: DNS still points to an old server, conflicting records exist, or the platform needs the exact records configured. Verify DNS with dig and remove stale entries.