01Who this is for
- Digital marketers who manage client domains need reliable DNS updates to configure sending domains.
- Ecommerce owners who connect email services to their stores must ensure DNS records are saved correctly.
- SaaS Founders integrating outbound email must verify their domain settings without interruption.
02DNS records, explained
The Chrome browser cannot commit DNS record changes in Squarespace; attempts appear to save but are not stored.
Using Firefox, Safari, or Microsoft Edge allows the DNS changes to be saved successfully.
Once saved in a supported browser, the records remain in place regardless of the browser used later.
03How businesses use DNS records
- Digital marketing agency. The agency opens Squarespace DNS settings in Firefox, re enters the required TXT and MX records, and saves them. The records then appear correctly, enabling the agency to complete domain verification.
- Ecommerce store. The store owner switches to Safari, adds the SPF and DKIM records required for their email provider, and confirms the changes. After saving, the store can send order confirmations without delivery issues.
- SaaS startup. The startup accesses Squarespace DNS via Microsoft Edge, re adds the domain verification CNAME, and saves. The domain becomes verified, allowing the startup to send onboarding emails.
04The numbers and rules that matter
- Propagation can take a few minutes up to 24 to 48 hours depending on the domain's TTL settings.
05How to set up and use DNS records in HighLevel
Switch browsers to edit DNS records in Squarespace
- Open your Squarespace domain and DNS settings using Firefox, Safari, or Microsoft Edge instead of Google Chrome.
- Re enter each DNS record you need, such as TXT, CNAME, or MX entries.
- Save the records; they should be stored without error.
06Things to know before you rely on it
- Google Chrome cannot save DNS record changes in Squarespace; only Firefox, Safari, and Microsoft Edge are supported for this task.
- After saving, DNS propagation may take from a few minutes up to 24 to 48 hours depending on the domain's TTL settings.
07If something goes wrong
- DNS changes do not appear to save when using Chrome. Repeat the addition or edit in Firefox, Safari, or Microsoft Edge and save again.
08How it connects to the rest of HighLevel
- Mailgun DNS setup guide Mailgun DNS guide
- Dedicated sending domain setup Dedicated domain
- Email best practice warm up guide Email warm up
Michael's take

Ever wonder why your DNS changes disappear after you click save in Squarespace? The culprit is Chrome.
If I were setting up a new sending domain, I’d open Squarespace in Firefox, add the required records, and double check they appear. A quick DNS lookup after a few minutes confirms everything is in place, and you avoid the Chrome snag entirely.