| Objective | Connect an AEserver-registered domain to a Squarespace website using DNS records. |
| Why customers use this | Professional branded website address; Cleaner marketing and SEO setup than using a default subdomain |
| Records to expect | Usually a verification CNAME plus several A records for the root domain and a CNAME for www, all shown in Squarespace. |
Before you start
Have access to both your AEserver Client Area and your account at Squarespace.
Know whether you are connecting the root domain (example.com), a subdomain (such as www.example.com or shop.example.com), or both.
Take a quick screenshot or copy of any current DNS records before editing them, especially if the domain already has a live website or email service.
Step 1 – Get the DNS records from Squarespace
1. Log in to Squarespace and open the site.
2. Go to Settings > Domains.
3. Choose Use a domain I own or the third-party domain option.
4. Enter your domain and copy all DNS records shown by Squarespace.
Step 2 – Add the records in the AEserver Client Area
1. Sign in to your AEserver Client Area.
2. Open Domains and select the domain you want to use.
3. Open DNS Management / DNS Zone.
4. Add the verification CNAME first, then the A records for the root domain, then the www CNAME.
5. Save your DNS changes.
Step 3 – Verify and finish
1. Return to Squarespace and wait for it to confirm the records. Once connected, set the preferred primary domain inside Squarespace if needed.
2. Allow time for DNS propagation. Many changes appear within a few minutes or hours, but full propagation can take up to 24-48 hours.
3. Once the service shows as connected, test the live result. Open the website, send a test email, or visit the exact subdomain you connected.
Benefits to highlight in the KB article
Professional branded website address
Cleaner marketing and SEO setup than using a default subdomain
Registrar and site platform stay separate, which can simplify ownership control
Quick tips
Leave existing MX records in place if you already use email
Squarespace often needs every record it shows, not just one of them
Verification can pass before the full website starts loading globally
Common issues and solutions
| Common problems | What it usually means / what to do |
| Connection stays in progress | One or more records may be missing or duplicated |
| Email stops working | MX, SPF, DKIM, or other mail records may have been removed accidentally |
| Wrong page loads on www | Re-check the www CNAME value and remove conflicting records |
If you are not sure which record to edit, or if the domain already has a working website or email service, contact AEserver Support before making changes so we can help you avoid downtime.
