DNS baseline — pragalva.me (2026-06-27)
Captured before any Cloudflare migration. This is the rollback reference: to undo a move, set Namecheap nameservers back to the two below and make sure these records exist.
Registrar / DNS
- Registrar + DNS host: Namecheap (BasicDNS)
- Authoritative nameservers (REVERT TARGET):
dns1.registrar-servers.comdns2.registrar-servers.com
- DNSSEC: OFF (no DS at parent, no DNSKEY, no RRSIG) — safe to flip nameservers without the DNSSEC dance.
Live records
| type | name | value | notes |
|---|---|---|---|
| A | pragalva.me (apex) | 76.76.21.21 | Vercel — the blog. Keep this; set DNS-only (grey cloud) in Cloudflare. |
| AAAA | apex | (none) | |
| CNAME/A | www.pragalva.me | (none) | blog is apex-only, no www |
| MX | pragalva.me | eforward1..3 (pri 10), eforward4 (15), eforward5 (20) .registrar-servers.com | Namecheap Email Forwarding. Dies on nameserver change. |
| TXT (SPF) | pragalva.me | v=spf1 include:spf.efwd.registrar-servers.com ~all | tied to the forwarding above |
| (subdomain) | vault.pragalva.me | (none yet) | the target for the new vault |
What the move affects
- Blog: zero downtime if the apex A is staged in Cloudflare before the nameserver flip (both providers answer the same IP during propagation).
- Email forwarding: HARD cutover. Namecheap forwarding only works on Namecheap nameservers; it stops the instant the flip happens. The
eforward*MX + SPF above become dead and must NOT be copied to Cloudflare. Replace with Cloudflare Email Routing if email is actually used. - Alias rules (
x@pragalva.me → destination) live in Namecheap’s Email Forwarding panel, NOT in DNS, so they are not captured above. Read them from the panel before migrating if email is in use.