Learn what happens if your custom domain still points to Webflow’s legacy DNS records.
Webflow has migrated its hosting infrastructure to Cloudflare. If your site was created before April 21, 2025, you must update your custom domain’s DNS settings as part of the migration.
As of January 13, 2026, you can’t publish to a custom domain that points to Webflow’s legacy DNS records. Please follow the instructions in the articles below to make the necessary changes to your DNS settings:
If your custom domain still points to Webflow’s legacy DNS records, your site will remain live, but you can’t publish changes. To re-enable publishing, update your custom domain’s DNS settings.
Note
Webflow only blocks publishing for domains
that still point to our legacy DNS records. If you use a reverse proxy,
you may still see “Update needed” in Site settings >
Publishing > Production even after
you’ve updated your proxy origin to Webflow’s new DNS records. In this
situation, you can ignore this message and continue publishing.
What happens after the January 13, 2026 deadline?
-
Publishing is blocked — you can't publish your site to your custom domain until your DNS records are updated.
-
Your site will remain on legacy infrastructure — if you haven't migrated to the new DNS records, your site isn't benefitting from Cloudflare’s performance and security features, including:
- Faster global response times
- Improved reliability and uptime
- Advanced DDoS protection
- Secure HTTPS connections via Cloudflare
-
Webflow may enforce DNS migration in the future — at some point, Webflow will need to migrate all remaining sites to the new DNS infrastructure. We’ll provide ample notice before this change, but if your site is still using legacy DNS settings at that time, it may go down.
Important
Your site will stay live, but you can’t publish or benefit from Webflow’s Cloudflare infrastructure until your DNS settings are updated. Update your DNS settings as soon as possible to avoid disruption.
Related articles
For more detailed guidance on the DNS migration, check out the following articles: