MCMC University

DNS Configuration Troubleshooter

⚠ DNS Resolution Error Detected

Your domain is experiencing a Cloudflare Error 1001 (DNS Resolution Error). This means Cloudflare's network received the request but cannot resolve your domain's DNS records. This is a DNS configuration issue — not a problem with your website code.

🔧 Fix for GoDaddy DNS + Cloudflare

Check Your Nameservers at GoDaddy

Log in to GoDaddy → My Products → DNS → Nameservers. If you're using Cloudflare, your nameservers should be set to the ones Cloudflare assigned you (e.g., ada.ns.cloudflare.com and bob.ns.cloudflare.com). If they still point to GoDaddy's defaults (e.g., ns01.domaincontrol.com), update them.

Verify DNS Records in Cloudflare

Log in to Cloudflare Dashboard → Select your domain → DNS tab. Ensure you have these records:
• A record for @ pointing to your server IP
• A or CNAME record for www pointing to your server IP or @
If your site is hosted on a platform (Vercel, Netlify, etc.), add the CNAME record they provide.

Disable DNSSEC at GoDaddy (if enabled)

DNSSEC conflicts with Cloudflare nameserver changes. In GoDaddy: DNS → DNSSEC → Disable. You can re-enable it later through Cloudflare's dashboard after your domain is active.

Unlock Your Domain at GoDaddy

Go to GoDaddy → Domain Settings → Ensure Domain Lock is OFF. A locked domain prevents nameserver changes from taking effect. You may see clientUpdateProhibited in WHOIS if locked.

Wait for DNS Propagation

DNS changes can take 24-48 hours to propagate globally. If you just made changes, wait and check again. You can reduce propagation time by lowering the TTL value in your DNS records before making changes.

Check if GoDaddy is Using Cloudflare Internally

GoDaddy sometimes uses Cloudflare in their own infrastructure. If you're NOT using Cloudflare directly but still see this error, contact GoDaddy support — the issue may be on their end.

☑ Quick Diagnostic Checklist

Nameservers at GoDaddy point to Cloudflare (not GoDaddy defaults)
DNS records exist in Cloudflare for @ (root) and www
DNSSEC is disabled at GoDaddy (can re-enable via Cloudflare later)
Domain is unlocked at GoDaddy (no clientUpdateProhibited)
Cloudflare shows domain status as "Active" (not "Pending")
SSL/TLS mode in Cloudflare is set to "Full" or "Full (Strict)"
No conflicting CNAME records pointing to Cloudflare-proxied domains
Waited at least 24 hours since last DNS change for propagation

🔍 Online Diagnostic Tools

Use these free tools to check your DNS configuration:

🌐 DNS Checker 🔧 MX Toolbox DNS Lookup 🚀 WhatsMyDNS 🔎 IntoDNS ☁ Cloudflare DNS Docs

Pro Tip: Enter your domain in DNS Checker to see if your nameservers are resolving correctly worldwide. If some regions show your site and others don't, DNS propagation is still in progress.

💡 Not Using Cloudflare Directly?

If you haven't set up Cloudflare yourself but are seeing this error, it's likely because GoDaddy uses Cloudflare internally for some of their hosting products. In this case:

Contact GoDaddy Support at +1 (480) 624-5500 or via live chat

Tell them: "I'm getting a Cloudflare Error 1001 DNS resolution error on my domain. Ray ID: 9c9cf06e5f832eea"

Ask them to verify your DNS records and check if their Cloudflare integration is configured correctly for your domain

Error detected at:

If this issue persists after following the steps above, contact your hosting provider.