Skip to content
Tutorials Center
My learning

Topics

Lesson 6 of 37 ยท Concepts and Setup

Domains, DNS and Hosting

Understand domain names, DNS records (A, CNAME, TXT, MX), SSL and hosting so you can connect a custom domain to a Wix or Webflow site and fix common propagation and email problems.

A free address like yourname.webflow.io is fine for testing, but a real site needs a real domain name: maple-bakery.com. Connecting a domain is one of the places where builder users most often get stuck, because it involves a system (DNS) that lives outside the builder and changes slowly. This lesson explains how domains, DNS and hosting fit together, how to read and write the records you will be asked for, and how to diagnose the common problems.

The exact buttons for connecting a domain differ between Wix and Webflow and change over time, so we describe the steps in general terms. Your builder's current instructions always list the precise records and values to use.

Three separate things

People say "my domain" when they mean three different services. Keeping them apart removes most confusion.

Service What it does Examples of who provides it
Domain registration You rent the name for a period, usually a year A registrar, or the builder itself
DNS Maps the name to servers and mail providers Registrar, builder, or a DNS provider
Hosting Stores and serves your site files Wix or Webflow hosting

You can buy the domain from a registrar, keep DNS there, and host the site at the builder. Or you can buy the domain inside the builder and let it manage everything. The second path is simpler. The first gives you independence if you later change builders.

How DNS works

The Domain Name System is the internet's phone book. Your registrar or DNS provider stores a set of records for your domain. When a browser asks "where is www.maple-bakery.com?", DNS answers with the records that match.

flowchart LR
  B["Browser"] --> R["Resolver<br/>(your ISP or public DNS)"]
  R --> T["Root and .com servers"]
  T --> N["Your domain's<br/>nameservers"]
  N --> R
  R --> B
  B --> H["Builder hosting<br/>serves the page"]

The resolver finds your nameservers, which return the record. Then the browser contacts the hosting server.

The records you will meet

Type Purpose Example
A Maps a name to an IPv4 address @ to 203.0.113.10
AAAA Maps a name to an IPv6 address @ to 2001:db8::10
CNAME Makes a name an alias of another name www to sites.example-host.net
TXT Holds text used for verification and email policy v=spf1 include:mail.example ~all
MX Says which servers receive email priority 10, mail.example.net

The values above use reserved documentation addresses and invented host names. Use the exact values your builder shows you. Two symbols recur: @ means the bare domain (maple-bakery.com), and www is a subdomain.

A bare domain (maple-bakery.com) cannot normally be a CNAME because the DNS rules require other records there, so builders usually ask for A records at the root and a CNAME for www. Some DNS providers offer special "flattening" or "ALIAS" records to work around this.

Connecting a domain: the general workflow

  1. Choose a primary address: with or without www. Pick one; the other will redirect to it.
  2. Add the domain in the builder (site settings, domains section). The builder displays the records it needs.
  3. Add the records at your DNS provider exactly as shown. Remove conflicting old records for the same name, especially old A records.
  4. Wait for propagation. DNS answers are cached for a time (the TTL, in seconds). It may take minutes to hours before everyone sees the change.
  5. Check the connection in the builder. It confirms when the records match.
  6. SSL certificate: after the domain is connected, the builder provisions an HTTPS certificate automatically. Do not enter payment or login details on a site that shows a browser security warning.
  7. Set the primary domain and confirm the other version redirects.

SSL and HTTPS

HTTPS encrypts traffic between visitor and server using an SSL/TLS certificate. Today every site should use it: browsers warn about non-HTTPS pages, and search engines prefer them. Both builders issue and renew certificates for connected domains without extra cost. If your site shows "Not secure", the common causes are a domain not fully propagated, a conflicting old DNS record, or hard-coded http:// links and images inside your content.

Email is separate from your website

Pointing your domain at a website host does not set up email. Email uses MX records for delivery and TXT records (SPF, DKIM, DMARC) for authentication. If you break MX records while editing DNS, email stops arriving. The golden rule: when you change website records, do not touch MX or TXT records unless you mean to.

Reading and checking records with code

A stand-in can model the rules a DNS checker applies. The next one validates a records list against a small set of mistakes beginners make. It does not talk to a real DNS server.

JS Stand-in: a DNS records sanity checker

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

No output.

Estimating propagation with TTL

DNS caches answer for the TTL you set. If a record has a TTL of 3600 seconds (one hour), resolvers that cached the old answer may keep it for up to an hour. A practical trick: before a planned move, lower the TTL to a short value (for example 300 seconds) a day ahead, make the change, then raise it again.

JS Stand-in: how long can the old answer survive?

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

No output.

Troubleshooting checklist

  • The builder says the domain is not connected. Compare each record's type, name and value with the instructions, character by character. Look for a trailing dot or a copied space.
  • Old site still showing. Old A records are still present, or the TTL has not expired.
  • Works with www but not without (or reverse). One of the two records is missing, or the redirect is not set.
  • Email stopped. MX or TXT records were deleted.
  • Browser shows a security warning. Wait for the certificate, check for conflicting records, and test in a private window.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which service stores the files and serves your pages?

    Hosting is where the site is stored and served. Registration rents the name and DNS maps it.
  2. 2. What does an A record do?

    An A record maps a hostname to an IPv4 address. A CNAME is the alias type.
  3. 3. You change website records and email stops. What is the likely cause?

    Email delivery depends on MX and TXT records, which are separate from the website's A and CNAME records.
  4. 4. Why lower the TTL before a planned DNS change?

    A short TTL limits how long resolvers keep serving the old answer after you switch.

Summary

  • Registration, DNS and hosting are three different services that can come from different providers.
  • Builders usually ask for A records at the root and a CNAME for www; use their exact values.
  • DNS changes take time because answers are cached for the TTL.
  • HTTPS certificates are issued automatically after the domain connects; conflicting records are the usual blocker.
  • Never disturb MX and TXT records when changing website records.

Next: Plans, Pricing and Workspaces