Substack Custom Domain Not Working

How to fix it

Try these in order — the most common fix is first.

1. 1. Compare records with what Substack shows

   Copy steps
   1. Open Settings > Domain in your publication dashboard
   2. Copy the host and value exactly into your DNS provider
   3. Remove conflicting old records for the same host
   Did this fix it? Yes No

2. 2. Turn off any DNS proxy

   Copy steps
   1. On Cloudflare switch the records to DNS only (grey cloud)
   2. Retry verification after a few minutes
   Did this fix it? Yes No

3. 3. Wait and verify propagation

   Copy steps
   1. Use a DNS lookup tool to confirm the record resolves to the right target
   2. Allow up to 36-48 hours before changing anything again
   Did this fix it? Yes No

4. 4. Contact Substack with a screenshot

   1. Send your full DNS record list and the domain name to Substack support
   Did this fix it? Yes No

Symptoms

Your domain shows an error, 404 or does not connect, or Substack reports Something went wrong when adding it.

Why it happens

• CNAME or A record mistyped or pointing elsewhere
• Cloudflare orange-cloud proxy enabled on the records
• DNS propagation still in progress (up to 36-48 hours reported)
• Conflicting old records at the registrar
• Domain not set up with www as expected

This guide also covers

• substack custom domain not working
• substack domain error
• substack cname
• substack something went wrong custom domain

Other Substack errors

• Substack Emails Going to Spam or Promotions
• Not Receiving Substack Emails
• Substack Login Link Not Arriving or Not Working
• Substack Paywall Showing for Paid Subscribers
• Substack Payment Declined When Subscribing
• Substack Stripe Payout Not Arriving
• Substack App Crashing or Not Loading
• Substack Can't Publish or Editor Page Unresponsive