How to set up DNS records for Shopify, Wix or Squarespace?
To set up DNS records for Shopify, Wix or Squarespace, you point your domain at the platform with two kinds of records at your DNS provider: one or more A records for the root domain (example.com) and a CNAME record for www. For Shopify, that's an A record to 23.227.38.65 and a CNAME from www to shops.myshopify.com. For Squarespace, it's four A records plus a CNAME from www to ext-sq.squarespace.com and a unique verification CNAME. For Wix, you either use the A and CNAME values shown in your Wix dashboard or switch your domain's nameservers to Wix. In every case, leave your email records untouched.
All three platforms walk you through the connection, and many can configure supported DNS providers automatically. When that doesn't work, or your domain is with a provider they don't recognise, you have to add the records yourself. This guide explains what each record does, gives the values for each platform, shows how to keep email working, and covers the checks and fixes for the problems people hit most often.
How Connecting a Domain Works
When you build a site on a hosted platform, it already lives at an address the platform gives you, such as your-store.myshopify.com or yoursite.wixsite.com. Connecting your own domain means two things:
- Telling the platform which domain to expect, so it knows which site to show and can issue an SSL certificate.
- Telling DNS to send visitors for your domain to the platform's servers.
The second part is done with records at whichever company hosts your DNS. That's usually your registrar, but it could be Cloudflare or another DNS provider. To find out, look up your nameservers:
dig example.com NS +short
ns1.registrar-dns.example.
ns2.registrar-dns.example.
Whoever runs those nameservers is where you'll add the records.
Why Two Record Types?
The root domain, also called the apex or naked domain, can't use a CNAME record. DNS rules don't allow a CNAME at the apex because it has to hold other records, such as NS and SOA. So the apex gets A records pointing at fixed IP addresses.
The www subdomain can use a CNAME, which points at a hostname owned by the platform. That lets the platform change its IP addresses later without you having to update anything.
Connecting a Domain to Shopify
In your Shopify admin, go to Settings > Domains and choose Connect existing domain. Enter your domain. If Shopify recognises your DNS provider, it may offer to connect automatically. Otherwise, add these records manually:
| Host | Type | Value |
|---|---|---|
@ | A | 23.227.38.65 |
www | CNAME | shops.myshopify.com |
In zone file format:
@ 3600 IN A 23.227.38.65
www 3600 IN CNAME shops.myshopify.com.
Some DNS dashboards ask for the host as @, some leave it blank, and some want the full domain. They all mean the apex.
Before adding them, delete any existing A record for @ and any existing A or CNAME record for www. Two A records on the apex, one pointing at Shopify and one at an old host, will send some visitors to the wrong place. Remove any old AAAA record on the apex too, unless Shopify's instructions tell you to add one.
Once the records are live, return to Settings > Domains and click Verify connection. Shopify then issues an SSL certificate, which can take up to 48 hours but usually happens much sooner. Finally, choose which domain is your primary domain, so the other one redirects to it.
Check the records:
dig example.com A +short
dig www.example.com CNAME +short
23.227.38.65
shops.myshopify.com.
Connecting a Domain to Squarespace
In Squarespace, open Settings > Domains (on newer accounts, the domains area of your site's settings), choose to use a domain you already own, and enter it. Squarespace then shows the records for your site. They follow a consistent pattern:
| Host | Type | Value |
|---|---|---|
@ | A | 198.185.159.144 |
@ | A | 198.185.159.145 |
@ | A | 198.49.23.144 |
@ | A | 198.49.23.145 |
www | CNAME | ext-sq.squarespace.com |
| Unique code | CNAME | verify.squarespace.com |
The last row is a verification record that's unique to your site. The host is a random string such as x7k2m9p4q1w8e5r3, and it proves to Squarespace that you control the domain. Copy it exactly from your Squarespace settings.
In zone file format, with an illustrative verification code:
@ 3600 IN A 198.185.159.144
@ 3600 IN A 198.185.159.145
@ 3600 IN A 198.49.23.144
@ 3600 IN A 198.49.23.145
www 3600 IN CNAME ext-sq.squarespace.com.
x7k2m9p4q1w8e5r3 3600 IN CNAME verify.squarespace.com.
All four A records are needed. They give Squarespace redundancy, and visitors' devices will try another address if one doesn't respond.
Check them:
dig example.com A +short | sort
dig www.example.com CNAME +short
dig x7k2m9p4q1w8e5r3.example.com CNAME +short
198.185.159.144
198.185.159.145
198.49.23.144
198.49.23.145
ext-sq.squarespace.com.
verify.squarespace.com.
Squarespace's domain panel shows the status of each record, and it typically marks the connection as complete within a few hours, though it can take up to 48 hours.
Connecting a Domain to Wix
Wix offers two ways to connect a domain you bought elsewhere:
- Nameservers: You change the domain's nameservers to the pair Wix gives you, and Wix hosts all of your DNS. This is the option Wix recommends.
- Pointing: You keep your current DNS provider and add an A record and a CNAME record that Wix gives you.
In your Wix dashboard, go to Domains, choose Connect a domain you already own, and follow the steps. Wix shows the exact values for whichever method you choose.
Wix via Pointing
With the pointing method, Wix asks you to set:
| Host | Type | Value |
|---|---|---|
@ | A | The IP address shown in your Wix dashboard |
www | CNAME | A hostname ending in wixdns.net, as shown in your dashboard |
Wix has changed its IP addresses over the years, and old guides on the web often show outdated values, so always copy them from your own dashboard rather than from a blog or forum post. As with the other platforms, remove conflicting A, AAAA and CNAME records first.
Wix via Nameservers
If you choose the nameserver method, Wix gives you two nameservers, which look like ns12.wixdns.net and ns13.wixdns.net. Enter them at your registrar in place of the existing ones.
This replaces your entire DNS zone. Records at your old DNS provider stop being used once the change takes effect, so before you switch:
- Note every record you have now, especially MX, SPF, DKIM, DMARC and any verification TXT records.
- Recreate them in Wix's DNS settings for the domain.
- Then change the nameservers.
You can check the delegation has updated by asking the TLD's servers:
dig @a.gtld-servers.net example.com NS +norecurse +noall +authority
example.com. 172800 IN NS ns12.wixdns.net.
example.com. 172800 IN NS ns13.wixdns.net.
That query works for .com and .net domains. For other TLDs, use dig example.co.uk NS +trace and look at the delegation from the TLD.
Platform Comparison
| Shopify | Squarespace | Wix | |
|---|---|---|---|
| Apex records | 1 A record | 4 A records | A record from dashboard |
www record | CNAME to shops.myshopify.com | CNAME to ext-sq.squarespace.com | CNAME from dashboard |
| Extra verification | No separate record | Unique CNAME | Not with nameservers |
| Nameserver option | No, records only | No, records only | Yes, recommended |
| Automatic setup | For supported providers | For supported providers | For supported providers |
Keeping Your Email Working
Connecting a website platform should never touch your email. Email is delivered according to your MX records, not your A or CNAME records, so as long as you leave MX, SPF, DKIM and DMARC records alone, mail keeps flowing.
Before you start, take a note of your current email records:
dig example.com MX +short
dig example.com TXT +short
dig _dmarc.example.com TXT +short
1 smtp.google.com.
"v=spf1 include:_spf.google.com ~all"
"v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"
Run the same commands after connecting the domain and make sure nothing has changed.
Two situations need extra care:
- Moving to Wix nameservers: As mentioned, you must recreate email records in Wix before switching.
- Automatic setup: When a platform configures DNS for you through an automated connection, it should only change website records. Check afterwards anyway.
If your store or site sends email itself, such as Shopify order confirmations from your own address, the platform will ask you to add extra records to authenticate that mail, usually CNAME or TXT records for DKIM. Add those exactly as shown, alongside your existing records. If you add or edit an SPF record, make sure you still have only one SPF record, because two SPF TXT records cause authentication failures.
Common Problems and Fixes
The Platform Says the Records Are Wrong
Check what the world actually sees with dig, and compare it with the platform's instructions. The most common causes are:
- A leftover A record from the previous host, so the apex has two different IPs.
- The host field filled in incorrectly, for example entering
example.comin a dashboard that automatically appends the domain, which createsexample.com.example.com. - A typo in an IP address or hostname.
You can catch the second one by querying the doubled name:
dig www.example.com.example.com CNAME +short
If that returns a value, the record was created with the wrong name.
Changes Haven't Shown Up Yet
DNS records are cached by resolvers for their TTL. If the old records had a TTL of a day, some visitors may see the old site for up to a day. To see the current value directly from your DNS provider, without caching, query its nameserver:
dig @ns1.registrar-dns.example example.com A +short
If that shows the right value, your configuration is correct and you just need to wait.
The SSL Certificate Won't Issue
The platform can only issue a certificate once your records point at it. If the records are right and the certificate is still pending after a day or two, check for a CAA record, which restricts which certificate authorities may issue for your domain:
dig example.com CAA +short
If it returns a list that doesn't include the authority your platform uses, the certificate can't be issued. Several hosted platforms, including Shopify and Squarespace, use Let's Encrypt. Check your platform's help pages, then add an entry for its authority, or remove the CAA record if you don't need it.
Cloudflare Proxy Interference
If your DNS is at Cloudflare and the records are proxied (the orange cloud), visitors connect to Cloudflare, not the platform. That usually stops the platform from verifying your records and issuing a certificate. Set these records to DNS only unless the platform specifically documents support for Cloudflare's proxy.
The www Version Works but the Root Doesn't (or the Reverse)
Make sure both records exist, and that you've chosen a primary domain in the platform's settings so the other one redirects. Test both:
curl -sI https://example.com | grep -iE '^(HTTP|location)'
curl -sI https://www.example.com | grep -iE '^(HTTP|location)'
HTTP/2 301
location: https://www.example.com/
HTTP/2 200
One should redirect and the other should return a 200 response.
A Short Checklist
- Find out where your DNS is hosted with
dig NS. - Note your current MX and TXT records.
- Start the domain connection in your platform's settings.
- Remove conflicting A, AAAA and CNAME records for
@andwww. - Add the A and CNAME records exactly as shown, plus any verification record.
- Check with
digthat the new values resolve. - Verify in the platform's dashboard and set your primary domain.
- Confirm HTTPS works and email records are unchanged.
FAQ: DNS for Shopify, Wix and Squarespace
An A record for the root domain pointing to 23.227.38.65 and a CNAME record for www pointing to shops.myshopify.com. Remove any older A or CNAME records for the same names first.
The four IP addresses give redundancy across Squarespace's infrastructure. All four should be present so visitors can still reach your site if one address is unavailable.
Wix recommends nameservers because it can then manage all records for you. Pointing with A and CNAME records is better if you want to keep DNS at your current provider, especially if you have email and other services there.
No, as long as you leave your MX, SPF, DKIM and DMARC records unchanged. The one exception is switching to Wix nameservers, where you must recreate your email records in Wix first.
Usually from a few minutes to a few hours, depending on the TTL of your old records. Platforms quote up to 48 hours to allow for slow caches and certificate issuance.
You can host your DNS at Cloudflare, but set the platform's records to DNS only rather than proxied. The proxy usually prevents the platform from verifying the domain and issuing its SSL certificate.
Conclusion
Connecting your domain to Shopify, Wix or Squarespace comes down to the same two records on every platform: A records for the root domain and a CNAME for www. Shopify uses one A record and shops.myshopify.com, Squarespace uses four A records, ext-sq.squarespace.com and a verification CNAME, and Wix gives you its values in the dashboard or asks you to switch to its nameservers.
Before you change anything, write down your email records, remove conflicting website records, and copy values exactly from the platform's instructions. Afterwards, check with dig that the new records resolve and your email records haven't changed. If something doesn't connect, a leftover record, a doubled hostname, a CAA restriction or a Cloudflare proxy is almost always the reason.
