Skip to content
Tutorials Center
My learning

Topics

Lesson 32 of 37 ยท Publishing and Maintenance

Domains, DNS and SSL

Connect a custom domain to Wix and Webflow: registrars, A, CNAME and TXT records, www versus root, SSL certificates, propagation and email records, with a runnable DNS checker.

When you publish, both platforms give you a free address such as yoursite.wixsite.com/name or yoursite.webflow.io. That is fine for testing, but a business needs its own domain, like example.com. Connecting one involves the Domain Name System (DNS), the internet's phone book, which turns names into server addresses. DNS looks technical, but it follows a small set of rules, and once you know them, the setup is a copy-and-paste job.

Wix and Webflow are hosted products and cannot run here. The values you must enter (IP addresses and target names) change over time and differ by plan, so always copy them from the dashboard screen shown during connection. The IP numbers in the examples below are fictional documentation addresses. The code is a stand-in DNS checker.

Ways to get a domain

  1. Buy through the platform. Wix sells domains and connects them for you; Webflow offers domain registration through its partner registrar in some regions, with simple connection. Easiest, since DNS is configured for you.
  2. Buy at a registrar (such as Namecheap, Cloudflare Registrar, Porkbun, GoDaddy and many others) and connect it. More choice and often cheaper renewals.
  3. Use a domain you already own and connect it, or transfer it into the platform.

Domains are rented per year. Turn on auto-renew and keep contact details current, and enable the registrar's transfer lock and two-factor sign-in. A lapsed domain can be lost to someone else.

DNS records you will meet

Record Purpose Example
A Points a name at an IPv4 address example.com to 203.0.113.10
AAAA Points a name at an IPv6 address rarely entered by hand
CNAME Makes a name an alias of another name www to cdn.platform-example.net
TXT Holds text for verification and email rules v=spf1 ...
MX Says which servers receive email mail.provider.com priority 10
NS Says which name servers answer for the domain set at the registrar

The part of the domain before the registered name is a subdomain: www in www.example.com. The bare example.com is the root (apex) domain, and a CNAME is normally not allowed at the root, which is why platforms ask for A records there (some DNS providers offer "ALIAS" or "CNAME flattening" as a workaround).

Two ways to connect

Point the name servers

You change the domain's name servers at the registrar to the platform's. The platform then controls all DNS records for the domain. Simple, but any other service (email, other subdomains) must be recreated in the platform's DNS panel. Wix offers this method ("point the domain to Wix").

Keep your DNS, add records

You leave name servers alone and add the records the platform gives you at your DNS host: typically A records for the root and a CNAME for www. This keeps email and other services untouched. Both Webflow and Wix support it ("connect"), and Webflow's Hosting settings show the exact records for your site.

Step by step: Webflow (typical)

  1. In Site settings, Publishing, choose Add custom domain and enter www.example.com and the root.
  2. Webflow shows the records to create (an A record or two for the root and a CNAME for www).
  3. At your DNS host, add those records. Remove conflicting old A or CNAME records for the same names.
  4. Return to Webflow and press verify; wait for the status to turn green.
  5. Choose which is the default (primary) domain. The other redirects to it (so example.com redirects to www.example.com or vice versa).
  6. Publish to the domain.

Step by step: Wix (typical)

  1. In the dashboard, Domains, choose Connect a domain you already own.
  2. Choose to connect via name servers or by adding records (A and CNAME).
  3. Follow the screen to the registrar and apply the values.
  4. Return and wait for the connection check; set the connected domain as Primary.

SSL and HTTPS

An SSL/TLS certificate encrypts traffic and shows the padlock; browsers warn on plain HTTP pages and search engines prefer HTTPS. Both platforms issue and renew certificates automatically once the domain points correctly (Webflow enables SSL in Hosting settings, and Wix provides it by default for connected domains). Certificate issuing can take from minutes to a few hours after DNS settles. If a certificate does not appear, check that no extra records conflict (for example an old A record pointing elsewhere) and that CAA records, if you have any, allow the platform's certificate authority.

After SSL is active, make sure all links and embedded resources use https://, to avoid "mixed content" warnings.

Propagation

DNS answers are cached for the time set in each record's TTL (time to live). After you change a record, different resolvers may show the old or new value until their caches expire, which can take minutes up to many hours (rarely up to a day or two). Lower the TTL (for example to 300 seconds) a day before a planned switch if your DNS host allows it.

A checker stand-in

DNS tools answer "is this record what the platform expects?" The stand-in below checks a list of records against expectations, using fictional addresses.

JS Stand-in: DNS record checker

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Email on your domain

A site's domain often carries email too. Keep the MX records for your email provider (Google Workspace, Microsoft 365, Zoho and others) when you connect the site. Add SPF, DKIM and DMARC TXT records so your mail and form notifications are trusted rather than spam-foldered. This is the same reason form notification emails sometimes land in spam (see Forms, Submissions and Notifications). The platform of your email provider gives the exact values.

The stand-in below parses an SPF record, which is the simplest of the three.

JS Stand-in: read an SPF record

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Redirecting variants

Visitors may type example.com, www.example.com, http:// or https://. Choose one canonical address, and make the rest redirect to it with a 301. Both platforms handle HTTP to HTTPS and www to root (or the reverse) once you set a primary domain.

Common mistakes

  • Leaving old A records in place next to the new ones.
  • Changing name servers without copying existing email (MX) records first, then losing email.
  • Entering https://example.com where only a host name is accepted.
  • Forgetting auto-renew and two-factor login at the registrar.
  • Testing right after the change and assuming it failed; wait for propagation.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which record points a name at an IPv4 address?

    An A record maps a name to an IPv4 address; CNAME makes an alias to another name.
  2. 2. Why do root domains usually need A records instead of CNAME?

    DNS standards generally disallow a CNAME alongside the other records at the root, so A records (or ALIAS flattening) are used.
  3. 3. What should you check before switching name servers?

    Changing name servers replaces all DNS records, so copy the ones you still need.
  4. 4. SSL certificates on these platforms are

    Both platforms provision HTTPS automatically once the domain points to them.

Summary

  • Use a custom domain; turn on auto-renew, transfer lock and two-factor sign-in.
  • A, CNAME, TXT, MX and NS records each have a job; copy values from the platform dashboard.
  • Connect either by pointing name servers or by adding records at your current DNS host.
  • SSL is automatic once DNS is right; allow time for propagation.
  • Protect email with MX, SPF, DKIM and DMARC.

Next: Publishing, Staging and Backups