DNS is configured correctly
Why it matters
Misconfigured DNS is one of the top launch-day failure modes for vibe-coded projects. A custom domain referenced in code but not pointed at the hosting provider produces broken canonical URLs, OAuth callback mismatches (login stops working), and email links that resolve to nothing. Under ISO 25010:2011 reliability.availability, this is a hard availability failure: the app is deployed but unreachable at its intended address. Because DNS propagation takes up to 48 hours, discovering this on launch day means a day of downtime.
Severity rationale
High because an unconfigured custom domain makes the production app unreachable and breaks every integration that depends on the canonical URL, from OAuth redirects to email links.
Remediation
Add your domain in the hosting platform dashboard first, then set the corresponding record at your registrar. For Vercel, the CNAME target is cname.vercel-dns.com; the A record target is 76.76.21.21.
// vercel.json
{ "domains": ["yourdomain.com", "www.yourdomain.com"] }
Verify propagation with dig yourdomain.com +short or whatsmydns.net before announcing launch. DNS changes require up to 48 hours to propagate globally — do not leave this for launch day.
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Pre-Launch Checklist Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- iso-25010:2011 · reliability.availability
Taxons
History
- 2026-04-18·v1.0.0·Initial import from pre-launch·automated