Check Updating DNS settings to find a list of registrars and links to their DNS setting documentation. Note: Some DNS hosting services prefer that you set the root domain () as the host instead of We recommend that you check the "Adding an A record" documentation of your DNS host. the ANAME or CNAME record on the root domain is.there are no A records on the root domain,.If you've set the root domain as the default domain on SSL hosting, make sure: You have only 2 A records for the root domain The A record values are: 75.2.70.75 & 99.83.190.102 (recommended).If the error is showing for your root domain, check the following if SSL is enabled: Make sure you only have the Webflow DNS records set on the root domain and/or the subdomain(s) hosted with Webflow.Make sure you're using the default nameservers of your DNS host.Then, you can setup the DNS records within the new registrar's dashboard. 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. Basically if the primary server went down, there's a backup server to ping to load up your site (simply a precaution).įor an optimal setup, we recommend that you add two A records. This isn’t an optimal setup, but your site will work.Īdding two A-Records helps with load balancing and redundancy in case anything happens to the primary server.
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. Make sure you have only one record for each subdomain and that it’s pointing to Webflow.
The same goes for CNAME records that you want to point to Webflow. Make sure to keep only the 2 Webflow records. Additional DNS recordsĪny additional A Records on the root domain will conflict with your Webflow A records. Webflow has separate servers and DNS records values for SSL hosting.
#Dnc server missing update
To point your domain to Webflow, follow the Connecting a custom domain tutorial.Īlso, make sure to update your DNS settings if you switch the SSL setting ON or OFF. This error also shows if you haven’t updated your domain DNS settings to point to Webflow. 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.Some ISPs ignore TTL settings and only update their cached records every two to three days. This speeds up web browsing and reduces traffic, which slows your propagation time. ISPs (Internet Service Providers) store your DNS settings locally rather than retrieving fresh data from your DNS server.We recommend that you keep the default value. Shorter TTL settings increase propagation speed but slows down your server's processing time. TTL (Time to Live) is the period of time that servers cache the information for your DNS records.Things that affect DNS settings propagation speed Here, you should see only the Webflow DNS record values.
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. 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. 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. For support, contact your registrar’s helpdesk or see their help documentation on nameservers. So, make sure you’re using the default nameservers of your registrar or DNS host. Webflow hosting doesn’t need custom nameservers - also called name servers or NS records.
#Dnc server missing how to
Here are the issues that may cause this error and how to fix them: If the connection is re-established, publish your site again.