Troubleshooting your DNS settings

When your custom domain isn’t pointing to Webflow correctly, you’ll see the “Unlinked” error 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.

Here are the issues that may cause this error and how to fix them:

Incorrect nameservers

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.

DNS propagation issues

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.

Things that affect DNS settings 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 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.

Additional DNS records

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.

Missing DNS records

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.

Fix your DNS settings

To make sure you're domain is correctly pointing to Webflow:

  1. Make sure you're using the default nameservers of your DNS host
  2. 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 that you have only 2 A records for the root domain (host=@), and that they are pointing to the Webflow’s servers.

  • If SSL is ON in your Webflow settings, the Webflow A record values should be: 34.193.69.252 & 34.193.204.92
  • If SSL is OFF in your Webflow settings, the Webflow A record values should be: 23.235.33.229 & 104.156.81.229

If you've set the root domain as the defualt domain on SSL hosting, make sure:

  • there are no A records on the root domain,
  • the ANAME or CNAME record on the root domain (host=@) is proxy-ssl.webflow.com.

Check and fix the CNAME record(s)

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.

  • If SSL is ON in your Webflow settings, the Webflow CNAME record values should be: proxy-ssl.webflow.com
  • If SSL is OFF in your Webflow settings, the Webflow CNAME record values should be: proxy.webflow.com
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.