Troubleshoot connection errors and DNS settings.
When your custom domain isn’t pointing to Webflow correctly, you’ll see a connection error message next to your domain name in your Custom domain settings under the Hosting tab of your Project Settings.
To verify that your DNS settings are correct and that your domain is correctly pointing to Webflow, click check status under each of your domain names.
If the connection is re-established, publish your site again. If not, continue this troubleshooter.
Webflow hosting doesn’t need custom nameservers — also called name servers or NS records. So, make sure you’re using the default nameservers of your registrar or DNS host. For support, contact your registrar’s helpdesk or see their help documentation on nameservers.
While most DNS hosts try to update your DNS records as fast as possible, many factors affect how long it takes and oftentimes are out of your DNS provider’s control. If you’ve waited 48 hours and your custom domain is still not pointing to your Webflow site, continue this troubleshooting tutorial or contact your DNS host’s helpdesk.
You can double check that your DNS records are live and pointing to Webflow by going to What's My DNS and entering your custom domain to check the A Records on your root domain and CNAME records for your subdomains.
Here, you should see only the Webflow DNS record values.
This error also shows if you haven’t updated your domain DNS settings to point to Webflow. To point your domain to Webflow, follow the Connecting a custom domain tutorial.
Also, make sure to update your DNS settings if you switch the SSL setting ON or OFF. Webflow has separate servers and DNS records values for SSL hosting.
Any additional A Records on the root domain will conflict with your Webflow A records. Make sure to keep only the 2 Webflow records. Check how to fix DNS issues below.
The same goes for CNAME records that you want to point to Webflow. Make sure you have only one record for each subdomain and that it’s pointing to Webflow. Check how to fix DNS issues below.
If you’ve only added one A record, or if your DNS provider only allows adding one A-Record, this connection error will show in your dashboard. This isn’t an optimal setup, but your site will work.
Adding two A-Records helps with load balancing and redundancy in case anything happens to the primary server. Basically if the primary server went down, there's a backup server to ping to load up your site (simply a precaution).
For an optimal setup, we recommend that you add two A records. And if your registrar doesn’t allow that, we recommend that you point your custom domain nameservers (NS records) to a third party DNS provider. Then, you can setup the DNS records within the new registrar's dashboard.
To point your domain to Webflow:
If the error is showing for your root domain, check the following if SSL is enabled:
If SSL is OFF (not recommended), the A record values should be: 126.96.36.199 & 188.8.131.52.
If you've set the root domain as the default domain on SSL hosting, make sure:
Note: Some DNS hosting services prefer that you set the root domain (yourdomain.com) as the host instead of @. We recommend that you check the "Adding an A record" documentation of your DNS host. Check Updating DNS settings to find a list of registrars and links to their DNS setting documentation.
If the error is showing for your subdomain(s), check that you have only one CNAME record for each subdomain, and that it is pointing to Webflow’s servers.
Note: Some DNS hosting services prefer that you set the full domain (www.yourdomain.com) as the host instead of www. We recommend that you check the "Adding a CNAME record" documentation of your DNS host. Check Updating DNS settings to find a list of registrars and links to their DNS setting documentation.
If your DNS settings are correct, but you’re experiencing issues with your published site, contact us and we’ll help you resolve any issues.
Something went wrong while submitting the form. Please contact firstname.lastname@example.org