How do I manually migrate my DNS records?

Updated

Manually migrate your DNS records to re-enable publishing and move to Webflow’s new hosting infrastructure.

Important

As of January 13, 2026, you can't publish to a custom domain that points to Webflow's legacy DNS records. After June 1, 2026, domains that still point to legacy records will experience downtime — your site will be unavailable to visitors until you update your DNS settings.

Note

If you’re using Cloudflare Orange-to-Orange (O2O), Zaraz, or a similar service with Webflow, follow the steps in the Using Cloudflare Orange-to-Orange (O2O) with Webflow article when migrating to our new hosting infrastructure.

On June 1, 2026, Webflow will begin turning off legacy hosting infrastructure. If your custom domain still points to legacy DNS records after this date, your site will experience downtime and be unavailable to visitors. Update your DNS settings as soon as possible to prevent downtime.

You can migrate your sites’ DNS records automatically or migrate manually with your domain registrar or DNS host.

You can find a list of all sites in your Workspace that have been published to custom domains, along with their current migration status (i.e., whether they’re connected to Webflow’s new DNS records or need to be migrated), in Workspace settings > Domain Updates.

Important

If your domain uses Cloudflare’s Zone Hold feature, SSL certificate generation may fail during connection or migration. This can prevent your site from going live or cause downtime if it was previously published.

This happens because Cloudflare blocks Webflow from issuing SSL certificates for held zones. To resolve the issue, release the Zone Hold in your Cloudflare account.

After your SSL certificate has been successfully generated, you can safely re-enable Zone Hold.

Pro tip

We recommend lowering the TTL (Time To Live) setting for your domain to the lowest value available (often 30 seconds) before updating your DNS records. This helps your changes propagate more quickly worldwide. After your migration is complete and your site is working as expected, you can restore your TTL setting to its previous value.

To manually migrate your DNS records:

  1. Go to the DNS settings for your custom domain (in your domain registrar or DNS host’s dashboard)

  2. Edit one of the two existing A records with the hostname @ and the value 75.2.70.75 or 99.83.190.102, and replace the value with 198.202.211.1

  3. Remove the other existing A record with the hostname @

  4. Edit the CNAME record with the hostname www and the value proxy-ssl.webflow.com and replace the value with cdn.webflow.com

  5. If your domain uses CAA (Certification Authority Authorization) records, update them to allow Webflow’s certificate providers

  6. Go to Site settings > Publishing > Production and click Check status

  7. Set a default domain to avoid SEO penalties for duplicate content

  8. Repeat the above steps for each site in your Workspace that requires DNS record migration (i.e., sites with a yellow Update needed status)

Important

If your domain uses CAA (Certification Authority Authorization) records, you’ll need to update them to allow Webflow’s certificate providers. Otherwise, SSL certificates for your site may fail to provision or renew. Learn how to configure CAA records for Webflow SSL.

You’ll need to repeat this process for all of your Workspaces where you’ve published sites to a custom domain. If your domain registrar or DNS host doesn’t let you edit an existing record, delete the old records and create new ones with the updated values instead.

Required plans

  • quickhelp

Related articles