Skip to main content

Setting up DNS on Google Domains (now Squarespace Domains)

Step-by-step instructions for connecting your Google Domains / Squarespace Domains domain to WedSites.

Written by Brian
Updated today

Setting up DNS on Google Domains (now Squarespace Domains)

Step-by-step instructions for connecting your Google Domains / Squarespace Domains domain to WedSites.

If you registered your domain with Google Domains (now owned by Squarespace), follow these steps to add the DNS records needed to connect it to your WedSites wedding website.

Before you start

Make sure you've added your domain to WedSites first. Go to Settings > General and enter your custom domain, then save. Then come back here to set up your DNS records.

You'll need access to your account.
- If you registered before the migration: Log in to your Squarespace account (Google Domains transferred to Squarespace in 2023)
- Your domain management works the same way, just with a different interface

About the Google Domains transition: Google Domains was sold to Squarespace in 2023. If you had a Google Domains account, it's now managed through Squarespace, but the DNS setup process is similar.

DNS records you need to add

You'll be adding these two records:

Type

Host

Data

TTL

A

@

37.16.10.26

1 hour

CNAME

www

domains.wedsites.com

1 hour

Important: You only need the A record if you're using an apex domain (like yourwedding.com). You only need the CNAME if you're using a subdomain (like www.yourwedding.com). We recommend adding both so both versions of your domain work.

Step-by-step instructions

For Squarespace Domains (post-migration)

If your domain is now in Squarespace:

Step 1: Log in to Squarespace

Go to squarespace.com and sign in to your account.

Step 2: Access domain settings

  1. Click Settings in the left sidebar

  2. Click Domains

  3. Click on the domain you want to connect

  4. Click DNS Settings or Advanced Settings

Step 3: Check for existing A records

Look for any existing A records with @ or blank in the Host column.

If you see existing A records for @:
- You need to delete any A records that don't point to 37.16.10.26
- Having multiple A records causes your domain to only work sometimes
- Click the X or Delete button next to each conflicting record

Common conflicting records to look for:
- Squarespace website hosting A records
- Old Google Sites or Google Workspace A records
- Parking page A records

Step 4: Add the A record

  1. Click Add Record or similar button

  2. Select A from the record type

  3. Fill in the fields:

    • Host: @ (or leave blank)

    • Data: 37.16.10.26

    • TTL: 3600 (1 hour) or leave default

  4. Click Save or Add

Step 5: Add the CNAME record

  1. Click Add Record again

  2. Select CNAME from the record type

  3. Fill in the fields:

    • Host: www (or your subdomain name if different)

    • Data: domains.wedsites.com

    • TTL: 3600 or leave default

  4. Click Save or Add

Using a custom subdomain? If you're using something like wedding.yourwedding.com instead of www, replace "www" with "wedding" in the Host field.

For legacy Google Domains interface

If you still have access to the old Google Domains interface:

Step 1: Log in

Go to domains.google.com and sign in.

Step 2: Access DNS settings

  1. Find your domain in the list

  2. Click Manage or DNS

  3. Click Custom records or Custom resource records

Step 3: Check for existing records

Look for any existing A records with @ in the Name/Host column.

If you see existing A records for @:
- Delete any A records that don't point to 37.16.10.26
- Click the trash/delete icon next to each conflicting record

Step 4: Add records

  1. In the Custom records section, you'll see fields for adding records

  2. For the A record:

    • Name: @ (or blank)

    • Type: A

    • TTL: 1 hour (or default)

    • Data: 37.16.10.26

  3. Click Add or Save

  4. For the CNAME record:

    • Name: www

    • Type: CNAME

    • TTL: 1 hour

    • Data: domains.wedsites.com

  5. Click Add or Save

After adding the records

Wait for DNS propagation. DNS changes usually take effect within 15-30 minutes, but can take up to 24-48 hours.

SSL certificate is automatic. Once your domain connects, we'll automatically add an SSL certificate so your site works with https. This happens within a few hours of your domain connecting.

Test your domain. After waiting, try visiting your domain in a browser. You should see your wedding website!

Troubleshooting

Domain not working after 30 minutes?
- Double-check that you entered the DNS records exactly as shown above
- Make sure you deleted any conflicting A records for @
- Verify you entered your domain in WedSites under Settings > General

Still seeing Google Sites or old website?
- Make sure you deleted the old A records
- Wait a bit longer for DNS propagation
- Clear your browser cache or test in an incognito window

Getting errors about "Squarespace-connected website"?
- If you have a Squarespace website connected to this domain, disconnect it first
- Go to your Squarespace site settings and remove the domain connection
- Then add the WedSites DNS records

CNAME record not saving?
- Make sure you don't have a trailing dot after domains.wedsites.com
- Verify the Host is "www" and not "@"
- Check that there are no conflicting CNAME records with the same name

Need to verify DNS setup?
- Go to dnschecker.org
- Enter your domain and select "A" record type
- You should see 37.16.10.26 in the results worldwide

Google/Squarespace-specific notes

Synthetic records: Google Domains/Squarespace shows "synthetic records" that are auto-generated. Don't worry about these — they won't interfere with your custom A and CNAME records.

Email forwarding: If you're using Google Domains/Squarespace email forwarding, it will continue to work after adding these DNS records (it uses separate MX records).

DNSSEC: If DNSSEC is enabled on your domain, it should work fine with these records. If you have issues, try temporarily disabling DNSSEC, adding the records, waiting for them to propagate, then re-enabling.

Related articles

Need help?

If you're stuck or something isn't working, reach out to our support team and we'll help you get your domain connected!

Did this answer your question?