Webflow sync, pageviews & more.
NEW

How do I get my Webflow site live when I am receiving a DNS probe finished nxdomain error and the CName setting is not propagating correctly?

TL;DR
  • Verify domain setup in Webflow’s Hosting settings and ensure it’s connected.
  • Check A records and CNAME in your domain registrar to match Webflow’s requirements.
  • Remove conflicting DNS records that interfere with proper resolution.
  • Use a DNS checker tool to confirm propagation status globally.
  • Flush local DNS cache if needed and test from a different network or incognito mode.
  • Allow up to 48 hours for full DNS propagation.

If your Webflow site isn’t going live and you're seeing a DNS_PROBE_FINISHED_NXDOMAIN error, it means there’s an issue with your domain’s DNS settings. The likely cause is an incorrect or unpropagated CNAME or A records.

1. Check Your Domain Configuration in Webflow

  • Go to Webflow’s Project Settings > Hosting tab.
  • Ensure your domain is correctly added and shows as Connected.
  • If it displays "Needs Attention," click the domain for more details.

2. Verify DNS Records in Your Domain Registrar

  • Webflow requires these DNS records for a custom root domain setup:

  • A Records:

    • (a) 75.2.70.75
    • (b) 99.83.190.102
  • CNAME Record:

    • Host: www → Points to: proxy-ssl.webflow.com
  • If using a www subdomain as the primary:

  • Only use the CNAME Record for www (do not set A records).

3. Clear Troublesome DNS Settings

  • Remove any conflicting records, such as old A, CNAME, or TXT records pointing to a different server.
  • Registrars like GoDaddy, Namecheap, and Google Domains may add default records—make sure they’re deleted if they interfere.

4. Check Propagation Status

  • Use DNS checker tools like https://dnschecker.org to see if your records have propagated globally.
  • Select A Record and CNAME Record searches based on what you’re troubleshooting.

5. Wait for DNS Propagation (or Force Refresh)

  • DNS changes can take a few minutes to 48 hours to fully propagate.
  • Try flushing your local DNS cache:
  • Windows: Open Command Prompt and type ipconfig /flushdns, then press Enter.
  • Mac: Use Terminal and type sudo killall -HUP mDNSResponder, then press Enter.

6. Test Your Site with an Alternate Connection

  • If the domain still doesn’t resolve, test with:
  • A different network (e.g., mobile hotspot).
  • A different device.
  • A browser in Incognito Mode to rule out caching issues.

Summary

Ensure your A and CNAME records are set up correctly in your domain registrar, remove conflicting DNS settings, and check propagation using a DNS checker. If necessary, flush your local DNS cache and test from another network. DNS changes can take up to 48 hours, so patience may be required.

Rate this answer

Other Webflow Questions