Fix Squarespace domain connection: when this repair path applies
Compare the current DNS zone with the records Squarespace expects for the connected site. Use these steps when one or more required DNS records are missing or conflicting, but first run the embedded diagnostic so the DNS resolution and delegation evidence supports this provider-specific path rather than a neighboring DNS, TLS, application or mail cause.
Find the authoritative setting before editing
Squarespace Domains/DNS settings or the external registrar/DNS provider shown by the active nameservers. For Fix Squarespace domain connection, confirm the active nameservers and exact service owner before changing check connection panel. A DNS-looking screen at squarespace has no public effect when another provider is authoritative for the zone.
Evidence to save for Fix Squarespace domain connection
Record the current public state for check connection panel, fix A/CNAME records, remove conflicts. This gives the repair a before/after comparison and prevents a cached answer or a separate working service from being confused with the configuration that produced the symptom.
- Check connection panel — Verify check connection panel from the public Internet and compare it with the value the responsible provider says should be live.
- Fix A/CNAME records — A CNAME aliases one hostname to another. Confirm the alias target is the provider-assigned hostname and that no conflicting address record exists at the same owner name.
- Remove conflicts — Verify remove conflicts from the public Internet and compare it with the value the responsible provider says should be live.
- Retest root and www — Verify retest root and www from the public Internet and compare it with the value the responsible provider says should be live.
Repair steps in squarespace
Compare the current DNS zone with the records Squarespace expects for the connected site.
- 1. Check connection panel. After this step, check the public value tied to check connection panel before changing another unrelated setting.
- 2. Fix A/CNAME records. After this step, check the public value tied to fix a/cname records before changing another unrelated setting.
- 3. Remove conflicts. After this step, check the public value tied to remove conflicts before changing another unrelated setting.
- 4. Retest root and www. After this step, check the public value tied to retest root and www before changing another unrelated setting.
Why this order matters for squarespace
The sequence begins with the provider/authority decision, then moves through check connection panel, fix A/CNAME records, remove conflicts. That keeps the change scoped to the failed DNS resolution and delegation path and avoids replacing nameservers, mail authentication or another healthy service just to make a provider dashboard indicator change.
Verify Fix Squarespace domain connection
Authoritative DNS should publish the intended record and independent resolvers should converge on that answer as their previous cached TTLs expire. Compare the same check connection panel and fix A/CNAME records evidence used before the change; a repair is complete when the public result agrees, not merely when the squarespace interface reports that a save succeeded.
If squarespace and the public result disagree
Check whether the edited zone is authoritative, whether the exact root/www/subdomain was changed, whether a proxy state alters the visible endpoint, and whether a prior TTL can still exist in recursive caches. Do not add a second conflicting check connection panel value to force validation.
Mistakes to avoid for this repair
Do not copy tenant-specific or region-specific values from another account, delete working email records during a website repair, change nameservers as a shortcut, or alter SSL/proxy modes without evidence from the origin. Fix Squarespace domain connection should change only the settings required by this diagnosis.
Technical references
These primary standards and provider documents are used to verify the behavior described on this page. Provider dashboards can change, so use the current official value for tenant-specific DNS records rather than copying an example from another account.