Webflow Custom DNS Setup Guide
Learn how to set up custom DNS for your Webflow site with step-by-step guidance to connect your domain correctly and avoid common errors.
Setting up custom DNS for your Webflow site can seem confusing if you are new to domain management. Many users struggle with connecting their domain properly, which can cause their website to be unreachable or display errors.
This guide explains how to configure your DNS settings for Webflow step-by-step. You will learn what DNS records to add, how to verify your domain, and troubleshoot common issues to get your site live smoothly.
What is Webflow custom DNS setup?
Webflow custom DNS setup means configuring your domain's DNS records to point to Webflow's servers. This allows your domain name to load your Webflow-designed website instead of a default Webflow URL.
By setting up custom DNS, you connect your purchased domain from registrars like GoDaddy or Namecheap to your Webflow project. This process involves adding specific A records and CNAME records in your domain's DNS settings.
Custom domain connection: It links your unique domain name to your Webflow site, making your website accessible via your branded URL instead of a Webflow subdomain.
DNS record configuration: You must add A records and CNAME records as specified by Webflow to your domain registrar’s DNS panel for proper routing.
Domain verification: Webflow verifies ownership by checking the DNS records, ensuring only authorized users connect domains to their projects.
SSL certificate activation: After DNS setup, Webflow automatically provisions SSL certificates to secure your site with HTTPS.
Understanding these basics helps you avoid common pitfalls and ensures your site loads correctly under your custom domain.
How do I find Webflow DNS records for my domain?
Webflow provides specific DNS records that you must add to your domain's DNS settings. These records include A records pointing to Webflow IP addresses and a CNAME record for the www subdomain.
You can find these DNS records in your Webflow project settings under the Hosting tab. Webflow updates these IP addresses occasionally, so always check your project for the latest values.
A records for root domain: Webflow requires two A records pointing to IPs like 75.2.70.75 and 99.83.190.102 to route your root domain correctly.
CNAME record for www: The www subdomain must have a CNAME record pointing to proxy.webflow.com to direct traffic properly.
Access via Hosting tab: You find these records by opening your Webflow project, navigating to Settings > Hosting, where Webflow lists the exact DNS entries.
Keep records updated: Always verify these records before updating your DNS to avoid downtime from outdated IP addresses or targets.
Following Webflow’s official DNS records ensures your domain resolves to your Webflow site without errors.
How do I add custom DNS records to my domain registrar?
Adding DNS records to your domain registrar involves logging into your domain account and editing the DNS or Zone file settings. Each registrar’s interface differs, but the process is similar.
You will add the A records and CNAME record provided by Webflow exactly as instructed. This step is critical to connect your domain to Webflow’s servers.
Login to domain account: Access your domain registrar’s dashboard where you manage your domain’s DNS settings or Zone Editor.
Add A records: Create two A records for your root domain with the IP addresses Webflow specifies, ensuring no typos or extra spaces.
Add CNAME record: For the www subdomain, add a CNAME record pointing to proxy.webflow.com to route www traffic correctly.
Save and propagate: After saving changes, DNS propagation can take up to 48 hours, but usually completes within a few hours.
Properly adding these DNS records is essential for your domain to resolve to your Webflow site without issues.
How do I verify my domain in Webflow after DNS setup?
After updating DNS records, you must verify your domain in Webflow to confirm ownership and enable publishing. Webflow checks if the DNS records match its requirements.
Verification happens automatically when you publish your site, but you can also manually check the domain status in your project settings.
Publish your site: Click the Publish button in Webflow to trigger domain verification and site deployment to your custom domain.
Check domain status: In Hosting settings, Webflow shows if your domain is connected, pending, or has errors based on DNS record correctness.
Wait for propagation: DNS changes can take time, so verification may show pending for several hours until DNS updates complete globally.
Troubleshoot errors: If verification fails, double-check DNS entries for typos or missing records and confirm no conflicting DNS settings exist.
Successful verification enables SSL and makes your Webflow site live on your custom domain.
What common DNS errors occur with Webflow custom domains?
Users often face DNS errors when setting up custom domains with Webflow. These errors usually stem from incorrect DNS records, propagation delays, or registrar restrictions.
Identifying and fixing these errors quickly helps avoid website downtime and ensures your site is accessible to visitors.
Incorrect A record IPs: Using wrong IP addresses causes your domain to fail resolving to Webflow servers, leading to site unavailability.
Missing CNAME for www: Without the www CNAME record pointing to proxy.webflow.com, the www version of your site won’t load properly.
DNS propagation delay: Changes can take up to 48 hours to spread worldwide, causing temporary site inaccessibility during this period.
Registrar DNS conflicts: Some registrars add default records or require special settings that can conflict with Webflow’s DNS, requiring manual cleanup.
Careful DNS configuration and patience during propagation help prevent these common issues.
How can I troubleshoot Webflow DNS setup problems?
If your Webflow site does not load after DNS setup, several troubleshooting steps can help identify and fix the problem. These steps focus on verifying DNS records and domain status.
Using online tools and Webflow’s support resources can speed up resolving issues.
Use DNS lookup tools: Websites like DNSChecker.org show if your DNS records have propagated and match Webflow’s requirements globally.
Verify DNS records manually: Log into your registrar and confirm A and CNAME records exactly match Webflow’s instructions without typos.
Clear browser cache: Sometimes cached DNS or site data causes loading errors; clearing cache ensures you see the latest site version.
Contact registrar support: If DNS changes do not apply or conflicts exist, your registrar’s support can help resolve domain-specific issues.
Following these steps usually resolves DNS setup problems and gets your Webflow site live under your custom domain.
Can I use subdomains or multiple domains with Webflow?
Webflow supports using subdomains and multiple custom domains on a single project. This flexibility allows you to create branded URLs for different site sections or markets.
You configure DNS for each domain or subdomain separately, then add them in Webflow’s Hosting settings to manage publishing.
Subdomain setup: Add CNAME records for subdomains pointing to proxy.webflow.com to host parts of your site on subdomains like blog.example.com.
Multiple domains: You can connect several domains to one Webflow project and choose a default domain for SEO and redirects.
Domain redirects: Webflow automatically redirects non-default domains to your primary domain to avoid duplicate content issues.
SSL for all domains: Webflow provisions SSL certificates for all connected domains and subdomains to keep traffic secure.
This capability allows you to customize your site’s domain structure to fit your branding and marketing needs.
Conclusion
Setting up custom DNS for your Webflow site is essential to use your own domain name and present a professional web presence. While the process involves technical steps, following Webflow’s instructions carefully ensures a smooth connection.
By adding the correct A and CNAME records, verifying your domain, and troubleshooting common errors, you can get your Webflow site live quickly and securely. Understanding DNS basics and registrar interfaces helps you maintain control over your domain and website.
What is the difference between A records and CNAME records in Webflow DNS setup?
A records point your root domain directly to Webflow’s IP addresses, while CNAME records alias subdomains like www to Webflow’s proxy server. Both are required for full domain connection.
How long does DNS propagation take when setting up Webflow custom domains?
DNS propagation usually completes within a few hours but can take up to 48 hours worldwide. During this time, your site may not be accessible on the new domain.
Can I use Webflow custom DNS setup with domains bought from any registrar?
Yes, Webflow supports domains from most registrars. You just need access to DNS settings to add the required A and CNAME records as Webflow specifies.
Why does my Webflow site show an error after DNS changes?
This often happens due to incorrect DNS records, missing www CNAME, or propagation delays. Double-check your DNS entries and wait for propagation to complete.
Is SSL included when I set up a custom domain with Webflow?
Yes, Webflow automatically provides free SSL certificates for all custom domains connected to your project, securing your site with HTTPS.