DNS Troubleshooting Guide: Resolving Third-Party Domain Connection Issues

DNS Troubleshooting Guide: Resolving Third-Party Domain Connection Issues

By Michael Thompson

January 16, 2025 at 01:18 AM

Third-party domain connections can fail for several reasons. Here's how to identify and fix common issues:

Initial Connection Period

Wait 24-72 hours after connecting your domain before troubleshooting, as DNS changes take time to propagate.

CNAME Record Issues

Two essential CNAME records are required:

  • One pointing to verify.squarespace.com
  • One pointing to ext-cust.squarespace.com

If experiencing issues, verify both records are properly configured in your domain provider's DNS settings.

A Record Configuration

When managing A records:

  • Delete any @ records that don't match Squarespace's four required records
  • Remove empty host records
  • Keep mail/email records to maintain email service

DNS table with red text

DNS table with red text

Resolving "Record Not Found" Errors

  1. Check the DNS settings panel for red labels
  2. Log into your domain provider
  3. Verify all DNS settings match Squarespace requirements
  4. Click Update in Squarespace's DNS panel
  5. Wait up to 72 hours for changes to take effect

Explanation of IP error 192.185.0.218

Explanation of IP error 192.185.0.218

Nameserver Troubleshooting

For Nameserver Connect:

  • Wait 72 hours for changes to propagate
  • If unsuccessful, restore provider's default nameservers
  • Manually connect using DNS records

For DNS Connect:

  • Avoid changing nameservers
  • Ensure nameservers point to your provider
  • Manually connect to Squarespace

SSL Certificate Issues

If you see security warnings or SSL certificate errors, consult the SSL Troubleshooting guide.

Domain Already Connected

If you receive a "domain already connected" error:

  1. Check your other Squarespace sites
  2. Disconnect the domain from the existing site
  3. Contact support if unable to locate the connected site

Obsolete Records

Replace any records labeled "No longer supported" with current DNS requirements to ensure proper SSL functionality.

If issues persist after following these steps, contact your domain provider for additional support.

Related Articles

Previous Articles