How to Connect Your Domain to Shopify, Wix, Squarespace & More (2025)

Quick Answer

Table of Contents

Before You Start

What You'll Need

1. Domain ownership - Access to your domain's DNS settings at your registrar
2. Website builder subscription - Most platforms require a paid plan for custom domains
3. 15-60 minutes - Initial setup time
4. Patience - DNS propagation takes 1-48 hours

Prerequisites Checklist

• Logged into your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.)
• Logged into your website builder admin panel
• Know where to find DNS settings at your registrar
• Have your target subdomain decided (www vs root domain vs both)
• Upgraded to a paid plan on your website builder (if required)

Important: Save Your Current DNS Records

Before making any changes, document your existing DNS records. Take a screenshot or write them down. If something goes wrong, you'll need these to restore your configuration.

Connection Methods Explained

There are two primary ways to connect a domain to a website builder:

Method 1: Change Nameservers

What it does: Hands complete DNS control to your website builder. All DNS records (A, CNAME, MX, TXT) are then managed in the builder's dashboard.

Pros:

• Simplest setup (often one-click)
• Platform handles SSL automatically
• Single place to manage everything
• Platform can optimize settings

Cons:

• Lose granular DNS control
• Must manage email DNS through builder
• Switching platforms requires DNS migration
• Some platforms have limited DNS options

Best for: Users who only need the website builder and prefer simplicity.

Method 2: Point DNS Records (A Record + CNAME)

What it does: Keeps DNS at your registrar but adds specific records pointing to the website builder's servers.

Pros:

• Keep control of DNS at registrar
• Easier to manage email separately
• Simpler to switch platforms later
• Can use advanced DNS features (like Cloudflare proxy)

Cons:

• More technical setup
• Must update records manually if builder changes IPs
• SSL setup may require additional steps
• More places to troubleshoot issues

Best for: Users who want flexibility, have email on separate servers, or prefer centralized DNS management.

Shopify Domain Connection

Shopify offers both methods: connecting via DNS records (recommended) or transferring the domain to Shopify.

Requirements

• Shopify plan: Any paid plan (Basic Shopify or higher)
• Domain: Must be a standard TLD (most extensions supported)

Method 1: Connect via DNS Records (Recommended)

This keeps your domain at your current registrar.

Step 1: Get Shopify's DNS Settings

In your Shopify admin, go to Settings > Domains > Connect existing domain.

Step 2: Add A Record for Root Domain

At your registrar's DNS settings:

Note: Delete any other A records for @ to avoid conflicts. Shopify may provide a region-specific IP (like 23.227.38.32) which is also valid.

Step 3: Add AAAA Record for IPv6 (Optional but Recommended)

Step 4: Add CNAME for www Subdomain

Important: Include the trailing period after shops.myshopify.com if your registrar requires it.

Step 5: Verify in Shopify

Return to Shopify admin, enter your domain, and click Verify connection. Shopify will check DNS records and enable SSL automatically (may take up to 48 hours).

Method 2: Transfer Domain to Shopify

Shopify can manage your domain entirely, including renewals.

Process:

1. Unlock domain at current registrar
2. Get authorization/EPP code
3. In Shopify: Settings > Domains > Transfer domain
4. Enter domain and authorization code
5. Approve transfer via email
6. Wait 5-7 days for transfer to complete

Cost: Shopify charges ~$15/year for .com renewals (market rate).

Shopify Troubleshooting

"SSL unavailable" error:

• Ensure both A and CNAME records are correct
• Remove any conflicting A records
• Wait up to 48 hours for SSL provisioning
• Check DNSSEC is disabled

Domain not connecting:

• Verify no wildcard records pointing at Shopify
• Disable Cloudflare proxy (orange cloud) if using Cloudflare
• Ensure exact record values (no typos)

Wix Domain Connection

Wix strongly recommends the nameserver method but supports DNS pointing.

Requirements

• Wix plan: Any Premium plan (Connect Domain or higher)
• Domain: Most TLDs supported

Method 1: Change Nameservers (Wix Recommended)

Step 1: Start Connection in Wix

Go to Wix Dashboard > Domains > Add an Existing Domain > Connect a domain you already own.

Step 2: Get Wix Nameservers

Wix will display nameservers like:

ns1.wixdns.net
ns2.wixdns.net

Step 3: Update at Your Registrar

At your registrar:

1. Find nameserver settings (often under "DNS" or "Nameservers")
2. Remove existing nameservers
3. Add Wix nameservers (usually 2)
4. Save changes

Step 4: Verify in Wix

Return to Wix and click Verify. Full propagation takes up to 48 hours.

Method 2: Point via DNS Records

If you need to keep DNS at your registrar:

Required DNS Records

Both records are required. If you only add one, your site won't work correctly and visitors may see security warnings.

Step-by-Step

1. In Wix: Domains > Connect a domain > Pointing (look for "advanced setup" option)
2. Copy the A record IP and CNAME value
3. At your registrar, add both records
4. Return to Wix and verify

Wix Limitations

Important restrictions:

• Wix does not support DNSSEC
• Wix does not support Cloudflare proxy (orange cloud)
• Disable both before connecting or DNS won't propagate

Wix Troubleshooting

"Domain not connected" after 48 hours:

• Verify both A and CNAME records are set
• Check for DNSSEC (must be disabled)
• Disable Cloudflare proxy if applicable
• Use whatsmydns.net to check propagation

"Not secure" warning:

• Both A record AND CNAME must be correct
• SSL certificate won't provision with incomplete records

Squarespace Domain Connection

Squarespace uses two CNAME records instead of the typical A record + CNAME approach.

Requirements

• Squarespace plan: Any paid website plan
• Domain: Most TLDs supported

Method 1: Nameserver Connect (Squarespace Recommended)

Step 1: Start in Squarespace

Go to Settings > Domains > Use a domain I own > Connect from provider.

Step 2: Get Squarespace Nameservers

Squarespace will display nameservers:

ns1.squarespace.com
ns2.squarespace.com
ns3.squarespace.com

Step 3: Update at Registrar

Replace existing nameservers with all three Squarespace nameservers.

Method 2: Connect via DNS Records

This method uses two CNAME records, one for verification.

Step 1: Get Your Unique Verification Code

In Squarespace: Settings > Domains > Use a domain I own > Connect from provider > Connect from your provider.

Squarespace generates a unique verification code for your site (looks like: abc123def456).

Step 2: Add Verification CNAME

Replace [unique-code] with the actual code from Squarespace.

Step 3: Add www CNAME

Step 4: Add A Records for Root Domain

Squarespace provides four A records in your DNS settings panel. Add all if possible:

If your registrar only allows one A record, use the first IP address provided.

Step 5: Verify Connection

Return to Squarespace and click Verify. The verification CNAME proves domain ownership.

Squarespace Troubleshooting

"Deprecated" warning in Squarespace DNS panel:

• Your records use old IP addresses
• Update A records to match current Squarespace requirements
• Old records may cause SSL issues

Verification CNAME failing:

• Ensure no typos in the unique code
• Some registrars need the full subdomain (code.yourdomain.com)
• Try TXT record verification as alternative

WordPress.com Domain Connection

WordPress.com (the hosted service, not self-hosted WordPress.org) offers domain mapping.

Requirements

• WordPress.com plan: Any paid plan (Personal or higher)
• Domain: Most TLDs supported

Method 1: Change Nameservers (WordPress.com Recommended)

Step 1: Start Connection

Go to My Site > Upgrades > Domains > Add new domain > Use a domain I own.

Step 2: Get WordPress.com Nameservers

WordPress.com provides three nameservers:

ns1.wordpress.com
ns2.wordpress.com
ns3.wordpress.com

Step 3: Update at Registrar

Replace existing nameservers with all three WordPress.com nameservers.

Method 2: Connect via DNS Records

For users who need to keep DNS elsewhere (e.g., to maintain email records).

Required DNS Records

Some registrars require the CNAME to point to the domain name directly:

Step-by-Step

1. In WordPress.com: Domains > Add domain > Use a domain I own > Map domain
2. Choose "advanced setup" or "I'll configure my own DNS"
3. Add the A records and CNAME at your registrar
4. Return to WordPress.com and verify

WordPress.com Email Warning

Important: When connecting via nameservers, your email may stop working. Before changing nameservers:

1. Note your current MX records
2. Connect the domain to WordPress.com
3. In WordPress.com DNS, add your MX records back
4. Test email before and after

If you have critical email, use the DNS pointing method instead of nameservers to avoid disruption.

WordPress.com Troubleshooting

Domain stuck on "Pending":

• DNS propagation can take 72 hours
• Verify all nameservers are correctly entered
• Check for typos

Email stopped working:

• MX records were lost during nameserver change
• Add MX records in WordPress.com DNS settings

Webflow Domain Connection

Webflow recently migrated to Cloudflare infrastructure (2025), so DNS requirements have updated.

Requirements

• Webflow plan: Site must be on a paid hosting plan
• Domain: Most TLDs supported

Important: 2025 DNS Migration

Webflow is migrating all sites to new Cloudflare-based hosting. All customers must update DNS by December 15, 2025. After this date, publishing to custom domains will be blocked until DNS is updated.

If you're setting up a new site, use the current (new) DNS records. If you have an existing site, check Webflow notifications for migration instructions.

Current DNS Records (2025)

Required Records

The TXT record value is found in Site settings > Publishing > Production and is unique to your site.

Step-by-Step Setup

Step 1: Add Domain in Webflow

Go to Site settings > Publishing > Add custom domain.

Step 2: Get Verification Code

Webflow shows a unique verification string starting with one-time-verification=.

Step 3: Add DNS Records at Registrar

Add all three records:

1. A Record: Points root domain to Webflow
2. CNAME: Points www to Webflow CDN
3. TXT: Proves domain ownership

Step 4: Verify in Webflow

Return to site settings and click Check status. Webflow will verify the TXT record and configure SSL.

For Sites Created Before April 21, 2025

If you have older DNS records, they may look like this:

A records: 75.2.70.75 and 99.83.190.102
CNAME: proxy-ssl.webflow.com

Update them to:

A record: 198.202.211.1 (remove the second A record)
CNAME: cdn.webflow.com

Webflow Troubleshooting

DNS not propagating:

• Lower TTL to 30 seconds before making changes
• Wait at least one full TTL period
• Check for conflicting A records

SSL not provisioning:

• All three records (A, CNAME, TXT) must be correct
• Wait up to 48 hours
• Verify TXT record exactly matches Webflow's value

Older site stuck:

• Check for in-app notification from Webflow
• Update to new IP and CNAME values
• Remove duplicate A records

Quick Reference Table

DNS Records Summary

Nameserver Reference

SSL Certificate Considerations

All major website builders provide free SSL certificates via Let's Encrypt or similar services.

How SSL Works with Custom Domains

1. You connect domain via DNS or nameservers
2. Platform verifies domain ownership
3. SSL certificate is automatically provisioned
4. HTTPS works within 24-48 hours

SSL Troubleshooting

"Not Secure" browser warning:

• SSL not yet provisioned (wait 24-48 hours)
• DNS records incomplete or incorrect
• Conflicting A or CNAME records

"Certificate doesn't match domain":

• DNS propagation incomplete
• Wrong records pointing elsewhere
• Try hard-refreshing browser (Ctrl+Shift+R)

Mixed content warnings:

• Site loads, but some resources still use HTTP
• Platform-side issue, check builder's help docs
• May need to update internal links to HTTPS

Forcing HTTPS

Most builders automatically redirect HTTP to HTTPS after SSL is configured. If not:

• Shopify: Automatic
• Wix: Automatic
• Squarespace: Settings > Domains > SSL > Secure
• WordPress.com: Automatic
• Webflow: Site settings > Hosting > Force SSL

Transfer vs Point: Which Should You Choose?

Transfer Domain to Website Builder

Choose this when:

• You only use the website builder (no separate email host)
• You want single-vendor simplicity
• You don't need advanced DNS features
• You're comfortable with the builder long-term

Considerations:

• Lock-in with that platform
• Renewals through their pricing
• Limited DNS customization
• Transfers out take 5-7 days

Point DNS Records (Keep Domain at Registrar)

Choose this when:

• You have email hosted elsewhere (Google Workspace, Microsoft 365)
• You want to easily switch website builders
• You need advanced DNS (Cloudflare features, etc.)
• You prefer centralized domain management

Considerations:

• Slightly more complex setup
• Must update records if builder changes IPs
• More places to troubleshoot

Point with Nameservers at Builder (Middle Ground)

Choose this when:

• You want easy setup but not full domain transfer
• You're okay managing DNS in the builder's dashboard
• Builder supports your email provider's MX records

Example: Move nameservers to Wix, then add MX records for Google Workspace in Wix DNS.

Common Mistakes and Fixes

Mistake 1: Forgetting to Remove Old A Records

Problem: Multiple A records cause intermittent connections (your site works sometimes).

Fix: Delete ALL existing A records for @ before adding the builder's A record.

Mistake 2: Adding CNAME for Root Domain

Problem: Most DNS providers don't allow CNAME records on the root domain (@).

Fix: Use an A record for root domain, CNAME only for www.

Exception: Some providers (Cloudflare) support "CNAME flattening" which allows CNAME-like behavior for root.

Mistake 3: Cloudflare Proxy Enabled

Problem: Some builders (Wix, partially Shopify) don't work with Cloudflare's orange cloud proxy.

Fix: Click the orange cloud to turn it gray (DNS only) for A and CNAME records pointing to your builder.

Mistake 4: DNSSEC Still Enabled

Problem: Wix and some others don't support DNSSEC, causing DNS resolution failures.

Fix: Disable DNSSEC at your registrar before connecting the domain.

Mistake 5: Not Adding Both A and CNAME

Problem: Site works at www.yourdomain.com but not yourdomain.com (or vice versa).

Fix: Always add both:

• A record for root domain (@)
• CNAME for www subdomain

Mistake 6: Wrong Priority for MX Records After Nameserver Change

Problem: Email stops working after moving nameservers to a website builder.

Fix: Re-add MX records in the builder's DNS panel with correct priority values.

Mistake 7: Typos in Record Values

Problem: DNS doesn't resolve because of small typos.

Fix: Copy-paste values directly from the builder's documentation. Watch for:

• Trailing periods (some require, some don't)
• Hyphens vs underscores
• Lowercase vs uppercase (DNS is case-insensitive, but copy exactly)

Propagation Time Expectations

What is DNS Propagation?

When you change DNS records, the changes must spread across DNS servers worldwide. This takes time because:

• DNS records are cached by ISPs and servers
• Cache duration is controlled by TTL (Time To Live)
• Different locations update at different speeds

Typical Propagation Times

How to Speed Up Propagation

1. Lower TTL before changes: Set TTL to 300 (5 minutes) at least 24 hours before making changes
2. Clear local DNS cache: ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache (Mac)
3. Use Incognito mode: Bypasses some browser caching
4. Test with external tools: whatsmydns.net shows global propagation status

Checking Propagation Status

whatsmydns.net: Enter your domain and record type to see propagation globally.

MXToolbox: mxtoolbox.com/SuperTool.aspx for detailed DNS lookups.

Google Admin Toolbox: toolbox.googleapps.com/apps/dig/ for DNS queries.

Troubleshooting

Domain Shows Old Website

Causes:

• DNS not fully propagated
• Browser cache
• ISP cache

Fixes:

1. Clear browser cache
2. Try incognito/private mode
3. Use a different network (mobile data)
4. Wait 24-48 hours
5. Check propagation with whatsmydns.net

Domain Shows "Site Not Found"

Causes:

• A record incorrect or missing
• Domain not verified in builder
• Builder plan expired

Fixes:

1. Verify A record value is correct
2. Check domain status in builder dashboard
3. Ensure hosting plan is active
4. Wait for propagation

Domain Shows "Not Secure" Warning

Causes:

• SSL certificate not provisioned
• Incomplete DNS setup
• Mixed content (HTTP resources on HTTPS page)

Fixes:

1. Wait 24-48 hours for SSL to provision
2. Verify all DNS records are correct
3. Check builder's SSL settings
4. Contact builder support if persists

www Works But Root Domain Doesn't (or Vice Versa)

Causes:

• Missing A record (root) or CNAME (www)
• Redirect not configured

Fixes:

1. Ensure both A and CNAME records exist
2. In builder settings, set primary domain and redirect
3. Most builders auto-redirect between www and non-www

Email Stopped Working

Causes:

• MX records lost during nameserver change
• MX records pointing to old server

Fixes:

1. Check MX records: dig MX yourdomain.com
2. Re-add MX records in current DNS location
3. If using nameservers at builder, add MX there
4. Contact email provider for correct MX values

Best Practices

Before Making Changes

1. Document current DNS records - Screenshot or write them down
2. Lower TTL - Reduce to 300-600 seconds, wait 24 hours, then make changes
3. Plan for downtime - Make changes during low-traffic periods
4. Have registrar login ready - Know your credentials before starting

During Setup

1. Follow builder's instructions exactly - Each platform has specific requirements
2. Add all required records - Don't skip the CNAME even if A record seems to work
3. Double-check for typos - Copy-paste when possible
4. Remove conflicting records - Delete old A/CNAME records that conflict

After Setup

1. Test thoroughly - Check root and www, HTTP and HTTPS
2. Verify SSL - Ensure padlock appears in browser
3. Test email - If you have email, confirm it still works
4. Monitor for issues - Check site daily for the first week

Long-Term

1. Document your setup - Note which records point where
2. Set renewal reminders - Domain and hosting renewals
3. Keep registrar contact current - Don't lose domain due to expired email

Frequently Asked Questions

How long does it take to connect a domain to a website builder?

Active setup takes 15-30 minutes. However, DNS propagation takes 1-48 hours (sometimes up to 72 hours for nameserver changes). Plan for your site to be fully working within 48 hours of making changes.

Can I use www.mydomain.com and mydomain.com?

Yes, all major website builders support both and automatically redirect one to the other. Set your "primary" domain in builder settings, and the other will redirect to it.

Should I transfer my domain to the website builder?

Generally, no. Keeping your domain at a dedicated registrar gives you more flexibility. If you switch builders later, you won't need to transfer the domain. However, if simplicity is your priority and you're committed to one platform, transferring can reduce complexity.

What happens to my email if I change nameservers?

Your email will stop working unless you re-add MX records in the new DNS location. Before changing nameservers:

1. Note your current MX records
2. Make the nameserver change
3. Immediately add MX records in the builder's DNS panel
4. Wait and test email

Using the DNS pointing method (A record + CNAME) avoids this issue entirely.

Can I connect subdomains to different platforms?

Yes. For example:

• yourdomain.com → Shopify (via A record)
• blog.yourdomain.com → WordPress (via CNAME)
• shop.yourdomain.com → Separate store (via CNAME)

Each subdomain can point to a different service.

Why is my site working on mobile but not desktop (or vice versa)?

This usually indicates incomplete DNS propagation. Different networks and devices may have different DNS servers with different cache states. Wait 24-48 hours for full propagation.

Do I need to do anything for SSL/HTTPS?

No additional action required with most builders. After DNS is verified, SSL certificates are automatically provisioned via Let's Encrypt. This typically takes 24-48 hours after DNS propagation completes.

Can I use Cloudflare with my website builder?

Yes, but with caveats:

• Shopify: Works, but don't use Cloudflare proxy (keep cloud gray)
• Wix: Does not support Cloudflare proxy at all
• Squarespace: Works with gray cloud only
• WordPress.com: Works with some configurations
• Webflow: Works, but may conflict with their Cloudflare integration

If using Cloudflare, disable the proxy (orange cloud → gray cloud) for records pointing to your builder.

Key Takeaways

• Two connection methods: Nameservers (easiest, full control to builder) or DNS pointing (more control, keep DNS at registrar). DNS pointing is usually more flexible.

• Most builders need both A and CNAME records: A record for the root domain (@), CNAME for www. Missing one causes issues.

• DNS propagation takes 1-48 hours: Don't panic if your site doesn't work immediately. Use whatsmydns.net to check propagation status.

• Wix and DNSSEC don't mix: Disable DNSSEC before connecting to Wix, and avoid Cloudflare proxy.

• Webflow has new DNS requirements (2025): If you have an existing Webflow site, update DNS before December 15, 2025.

• Protect your email: If changing nameservers, immediately re-add MX records in the builder's DNS to avoid email downtime.

• SSL is automatic: All major builders provision free SSL certificates automatically after DNS is verified.

Next Steps

1. Choose your connection method: Nameservers for simplicity, DNS pointing for flexibility
2. Follow the platform-specific guide above for your builder
3. Test your setup using whatsmydns.net and by visiting your domain
4. Verify SSL works (check for padlock in browser)
5. Test email if you have MX records configured

Related Articles

• How to Change Nameservers
• Point Domain to Website Guide
• DNS Record Types Explained
• Troubleshooting Slow DNS Propagation
• Domain Forwarding Setup

Research Sources

• Shopify: Connect Your Domain Manually - Official Shopify documentation
• Shopify: Editing DNS Settings - Shopify DNS management
• Wix: Connecting via Pointing Method - Wix pointing guide
• Wix: Resetting A and CNAME Records - Wix DNS reference
• Squarespace: DNS Records for Third-Party Domains - Squarespace DNS requirements
• WordPress.com: Connect a Domain - WordPress.com domain guide
• WordPress.com: Manage DNS Records - WordPress.com DNS management
• Webflow: Manually Connect a Custom Domain - Webflow DNS setup
• Webflow: Update DNS for Cloudflare Migration - Webflow 2025 migration