Wix DNS

A Webflow-hosted site needs DNS records that route its domain to Webflow hosting servers, and those records live wherever the domain is managed. For a Wix-registered domain, that is the Wix account, and Wix locks the nameservers for domains registered there. Manual configuration inside the Wix account handles the required A, CNAME, and TXT records.

The connection uses records copied from Webflow Site settings and checked after they are added to Wix. SSL provisions automatically once the records resolve.

An agency or small business owner can move a Wix site to Webflow while keeping the existing domain and Wix-bundled email arrangement. Marketing teams can also launch a Webflow campaign page on a subdomain of a Wix-managed domain while the main site remains unchanged.

How to integrate Wix DNS with Webflow

What is Wix DNS? Wix DNS is the DNS record management panel inside the Domains section of a Wix account. It lets you edit A, CNAME, MX, TXT, SPF, and SRV records. That covers domains purchased from Wix and external domains connected to Wix through nameservers. NS records are viewable but locked, and Wix does not support CAA records.

Teams use this combination during Wix-to-Webflow migrations when the site moves while the domain and email remain at Wix. It also covers a Webflow page on a subdomain like launch.yourdomain.com while Wix serves the root. Webflow's guide to migrating a live site names Wix as a source platform and lists the same A record and CNAME as the manual connection guide.

This connection sits outside the Webflow Marketplace app catalog. Wix DNS-Webflow integration uses two approaches:

• Manual DNS records in the Wix panel handle the root, www, and subdomain connections without writing code.
• The Webflow Data API and Wix Domain DNS API give you programmatic control over record updates and publishing and require server-side development with an account-level Wix API key.

The API path is worth the setup when you manage many client domains.

Point a Wix domain to Webflow with manual DNS records

A paid Site plan and access to the Wix account that manages the domain are required for this method. Follow Webflow's manual custom domain steps and make the corresponding changes in Wix. The process applies to domains purchased from Wix and external domains connected to Wix through nameservers.

The manual workflow connects the root and www domains and verifies ownership. It can also delegate a subdomain to a separate Webflow site.

For a domain connected to Wix by pointing, the external DNS host stores the records, and Wix says to edit them there instead.

Get the DNS values from Webflow

The site's creation date determines which hosting records appear in Site settings. Copy the exact values shown for your site because older and newer sites can have different requirements.

To get the values:

1. Open Site settings > Publishing > Production and click Add a custom domain.
2. Choose Manually add domain, enter your domain, and click Add domain. Add both the root domain and the www subdomain.
3. Copy the records listed for each domain.

For sites created after April 21, 2025, the records are:

• An A record with the Host Name @ that points to 198.202.211.1
• A CNAME record with the Host Name www that points to cdn.webflow.com
• A TXT record with the Host Name _webflow, containing the one-time-verification=… string shown in Site settings

Sites created before April 21, 2025 may still require two A records, so check the Production tab for your specific site. Webflow blocked publishing to the legacy values 75.2.70.75, 99.83.190.102, and proxy-ssl.webflow.com on January 13, 2026, per Webflow's Cloudflare migration.

Add the records in the Wix DNS panel

The @ and www hostnames require specific handling in Wix. Leave the Wix Host Name field blank when Webflow shows @. Wix reserves www for connecting a Wix site, so update the existing CNAME for that hostname. Wix documents both rules in its guide to managing DNS records.

To add the records:

1. In your Wix account, go to Domains, click the Domain Actions icon, and select Manage DNS records.
2. In the A (Host) section, hover over the existing A record and click Edit, or click + Add Record. Leave Host Name blank, enter the A value copied from Site settings, and click Save.
3. In the CNAME section, hover over the existing www record and click Edit. Replace the Value with the CNAME value copied from Site settings and click Save.
4. In the TXT section, click + Add Record. Enter the verification hostname, paste its string into Value, and click Save.
5. Delete any remaining old A records from the actions icon beside each record, then confirm in the Delete Record pop-up.

Adding a second www CNAME produces Wix's "Hostname already in use" error. Wix also states that changing the TTL value does not speed up how fast a record propagates, and only changes how long cached information is stored. Wix and Webflow both warn that leftover A records conflict with the new one, so remove them.

Verify the connection and set the default domain

DNS propagation can take up to 48 hours, although the Production tab often validates the records sooner. The default domain controls the root-versus-www redirect, so Wix needs no redirect records.

To verify and finish:

1. In Site settings > Publishing > Production, click Check status under each domain name.
2. If a domain shows an error, wait and recheck; propagation can take up to 48 hours.
3. Click Make default next to the version you want visitors to land on.
4. Publish the site.

Set a default domain covers how all other connected domains redirect to the default. SSL is enabled by default for sites created after November 14, 2018, and SSL hosting states that certificates renew automatically as long as DNS continuously points to Webflow. The Wix domain is no longer serving a Wix site at this point, which is expected. Resetting its A and CNAME records to their Wix defaults would undo the Webflow connection.

Cut over a live site without downtime

DNS caches keep serving the old destination until their stored records expire. Prepare redirects and reduce TTL before changing the destination of a live Wix domain.

To cut over a live site:

1. Crawl the existing Wix URLs and map each one to its new Webflow path.
2. Import the 301 redirects into Webflow through Import/export 301 redirects before touching DNS.
3. Lower the TTL on the A and CNAME records in Wix to 30 seconds, at least one full TTL period before the switch.
4. Apply the records copied earlier, then publish.

Webflow's Wix migration guide puts redirects before the domain cutover to prevent traffic loss during launch, and it is also where the 30-second TTL recommendation comes from. A lower TTL shortens how long resolvers cache the old records; it does not make the new records reach resolvers faster.

Connect a subdomain to a separate Webflow site

A hostname such as launch.yourdomain.com or blog.yourdomain.com can route to its own Webflow site while Wix or another platform continues serving the root. Each connected subdomain requires a separate Webflow site with its own paid Site plan.

To connect a subdomain:

1. In the Webflow site for the subdomain, open Site settings > Publishing > Production, click Add a custom domain, choose Manually add domain, and enter the full subdomain.
2. In Wix, go to Domains > Domain Actions > Manage DNS records, then click + Add Record in the CNAME section.
3. Enter the subdomain prefix (for example, launch) as the Host Name and the CNAME value shown in Site settings, then click Save.
4. Add the verification TXT record shown in Site settings, click Save Changes, then click Check status in Webflow.

Adding a CNAME for one host name leaves the root A record and the MX records untouched. Wix's guide to connecting a subdomain sets two limits: the steps do not apply when the main domain is connected to Wix by pointing, and the subdomain has to sit in the same Wix account as its main domain. Wix separately states that connecting a business email to a subdomain is not currently possible. For the Webflow half, see manually connect a subdomain.

Build with the Webflow and Wix Domain DNS APIs

Account-level authentication and server-side development are prerequisites for scripting the DNS change, publishing the Webflow site, and confirming publication through a webhook. The Wix side authenticates with an account-level API key, which the standard authorization header cannot replace. The Wix Domain DNS API covers Wix-registered domains and external domains connected by nameservers, and excludes domains connected to Wix by pointing. Adding the custom domain to the site remains a manual step in Site settings > Publishing > Production.

The APIs involved:

• The Wix Domain DNS API handles reading a DNS zone and adding or deleting records in one call
• Webflow's Data API handles reading a site's custom domains and publishing to them
• Webflow webhooks fire site_publish events your server can act on

Confirm a Wix DNS update by calling Get DNS Zone again after the PATCH, because the Domain DNS API reference documents no events for DNS record changes.

Update A and CNAME records with the Wix Domain DNS API

One PATCH request can add the current Webflow records and remove a legacy A record atomically.

To update the zone:

1. Call GET https://www.wixapis.com/domains/v1/dns-zones/{domainName} with your account-level API key to read the current records.
2. Call PATCH https://www.wixapis.com/domains/v1/dns-zones/{domainName} with a body shaped like this, using the host name format from the Update DNS Zone reference:

   {
     "additions": [
       {
         "type": "A",
         "hostName": "yourdomain.com",
         "values": ["198.202.211.1"]
       },
       {
         "type": "CNAME",
         "hostName": "www.yourdomain.com",
         "values": ["cdn.webflow.com"]
       }
     ],
     "deletions": [
       {
         "type": "A",
         "hostName": "yourdomain.com",
         "values": ["75.2.70.75"]
       }
     ]
   }

3. Call Get DNS Zone again to confirm the additions landed and the deletions cleared.

The request body fields are additions.type, additions.hostName, additions.values, and optional additions.ttl in seconds, plus deletions.type, deletions.hostName, and deletions.values. The call carries wix-account-id and Authorization headers and cannot use the standard authorization header. Wix states that the name server records for a Wix domain cannot be updated.

Publish the Webflow site to the connected domain

The custom domains endpoint returns the domain IDs required by the publish endpoint after DNS resolves and the domain exists in Site settings.

To publish programmatically:

1. Call GET https://api.webflow.com/v2/sites/{site_id}/custom_domains with the sites:read scope. The response returns customDomains, each with an id, url, and lastPublished value.
2. Call POST https://api.webflow.com/v2/sites/{site_id}/publish with the sites:write scope and this body:

   {
     "customDomains": ["<custom_domain_id>"],
     "publishToWebflowSubdomain": false
   }

3. Check for an HTTP 202 response containing customDomains, publishToWebflowSubdomain, and publishScope (site or page).

The Publish Site reference requires at least one of customDomains or publishToWebflowSubdomain in the body. The optional pageId field limits publication to a single page.

Confirm publishes with the site_publish webhook

The domains array in a site_publish event identifies every destination reached by a publish. Register the webhook once per site with the sites:write scope to close the loop after a DNS change.

To register and verify the webhook:

1. Call POST https://api.webflow.com/v2/sites/{site_id}/webhooks with "triggerType": "site_publish" and your callback url.
2. On each incoming request, read the x-webflow-timestamp and x-webflow-signature headers.
3. Concatenate timestamp + ":" + JSON.stringify(request_body), compute an HMAC-SHA-256 with your signing key, and compare it to the signature header. Reject requests whose timestamp is older than 5 minutes.
4. Read siteId, publishedOn, domains, and publishedBy, and publishScope from the payload.

Match the domains array against the URL returned by Get Custom Domains. For site-token webhooks created after April 14, 2025, each webhook has its own secret key, per Working with Webhooks.

What you can build with the Wix DNS Webflow integration

Record-level control supports migrations, split-domain architectures, campaign subdomains, and scripted cutovers.

• Client migration with email intact: An agency follows the live-cutover workflow for a client's Wix site, including the imported 301 redirects.
• Campaign landing page on a subdomain: A growth team uses the subdomain workflow for launch.yourdomain.com and ships a Webflow landing page while the root domain stays where it is.
• Marketing site at the root, store on a subdomain: brand.com points to Webflow, and shop.brand.com points to a store platform through a separate CNAME.
• Scripted cutovers across client domains: An agency ops team calls Update DNS Zone for each Wix-registered client domain, publishes each Webflow site through the Publish Site endpoint, and logs site_publish webhook payloads to confirm which domains went live.

For bulk updates across many client domains, the API path can patch each DNS zone, publish the corresponding Webflow site, and log the domains returned by each webhook.