When your custom domain isn’t pointing to Webflow correctly, a connection error message will appear under your domain name in Site settings > Publishing tab > Production.
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, please continue the following troubleshooting steps.
In this lesson, you’ll learn:
Issues that may cause the “Issues detected” error message
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, or that you’re managing your DNS records with the host where your NS records are pointed.
For support, contact your DNS host’s helpdesk or check out their documentation on nameservers.
DNS propagation issues
While most DNS providers try to update your DNS records as fast as possible, many factors impact how long it takes for your site to appear on your custom domain, including TTL (time to live) and internet service providers. DNS changes can take up to 48 hours to fully propagate in all geolocations, although this typically occurs within a few hours, so it may be a matter of waiting a bit longer for the site to “come online.”
You can double-check that your DNS records are correct and view the propagation status using a tool like whatsmydns. Only the Webflow DNS record values should appear as A and CNAME records for your root domain and subdomains.
If your domain isn’t working correctly after 48 hours, please troubleshoot your DNS settings or contact your domain provider’s help desk. If your DNS settings are correct, but you’re still experiencing issues with your published site, please contact Webflow’s customer support team.
Factors that affect DNS propagation speed:
- TTL (Time to Live) is the period of time that servers cache the information for your DNS records. Shorter TTL settings increase propagation speed but slows down your server’s processing time. We recommend that you keep the default value.
- ISPs (Internet Service Providers) store your DNS settings locally rather than retrieving fresh data from your DNS server. This speeds up web browsing and reduces traffic, which slows your propagation time. Some ISPs ignore TTL settings and only update their cached records every two to three days.
- Some DNS hosts often protect their root nameservers from overuse by setting a high TTL of up to 48 hours and some ISPs cache the information anyway, which can result in a longer propagation time.
Incorrect DNS records
This error also shows if you haven’t updated your domain DNS records to point to Webflow. To point your domain to Webflow, check out our guide to manually connecting a custom domain. Depending on your DNS host, you may also be able to quick connect your custom domain to Webflow to update your DNS records automatically.
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. Learn more about DNS settings for SSL and non-SSL hosting.
Additional DNS records
If you have any additional A records on your root domain (besides the 2 Webflow A records), they’ll conflict with the A records you’ve set to point to Webflow. Make sure to remove any additional A records.
The same is true for CNAME records. Make sure you only have 1 record for each subdomain you’ve connected to your Webflow site, and that the record points to Webflow.
Missing DNS records
If you’ve only added a single A record, or if your DNS provider only allows you to add a single A record, the connection error will appear.
While your site should still load with a single A record, we strongly recommend using both A records to help with load balancing and redundancy — that way, if the primary server (one of the IPs) goes down, there’s a backup server to serve your site and avoid any downtime or outages.
In cases where you’re unable to add both A records with your DNS provider, we recommend pointing your domain nameservers (NS records) to a third-party DNS provider like Cloudflare so you can manage your DNS records there. Learn more about connecting a custom domain with Cloudflare.
How to fix your DNS settings
To point your domain to Webflow:
- Make sure you’re using the default nameservers of your DNS host
- Make sure you only have the Webflow DNS records set on the root domain and/or the subdomain(s) hosted with Webflow
Check and fix the A records
If the error is showing for your root domain, check the following if SSL is enabled:
- You have only 2 A records for the root domain (with the hostname @)
- The A record values are: 184.108.40.206 and 220.127.116.11 (recommended)
- The A records 18.104.22.168 and 22.214.171.124, and 126.96.36.199 and 188.8.131.52 will work also, but we highly recommend you use the ones mentioned above
If SSL is not enabled (not recommended), the A record values should be: 184.108.40.206 and 220.127.116.11.
If you've set the root domain as the default domain on SSL hosting, make sure:
- There are no A records on the root domain
- The ANAME or CNAME record on the root domain (with the hostname @) is proxy-ssl.webflow.com
Note: Some DNS providers prefer that you set the root domain (e.g., yourdomain.com) as the hostname instead of @. We recommend that you check your DNS provider’s documentation to confirm their preferences and requirements. Check out this list of DNS providers and links to their documentation on updating DNS settings.
Check and fix the CNAME record(s)
If the error is showing for your subdomain(s), check that you have only 1 CNAME record for each subdomain, and that the record points to Webflow’s servers.
If SSL is enabled in your Webflow settings, the Webflow CNAME record value should be proxy-ssl.webflow.com. If SSL is not enabled in your Webflow settings, the Webflow CNAME record value should be proxy.webflow.com.
Note: Some DNS providers prefer that you set the www subdomain (e.g., www.yourdomain.com) as the hostname instead of www. Additionally, some DNS providers require a trailing dot at the end of CNAME records (e.g., proxy-ssl.webflow.com.). We recommend that you check your DNS provider’s documentation to confirm their preferences and requirements. Check out this list of DNS providers and links to their documentation on updating DNS settings.
Still having issues?
If your DNS settings are correct, but you’re experiencing issues with your published site, please contact our customer support team and we’ll help you resolve any issues.