Hey all! I've had my rounds with support about this issue. I did find a solution. Delete the squarespace defaults under DNS. Add your forwarding rule with just the @. If it won't let you save, do a hard refresh, log back in, do it again, and it will work. I selected the SSL options (not sure if this matters). After the rule is in place, head back to DNS and add the squarespace defaults again. Give it a couple and your root & www will forward just fine. The interesting thing is adding a root forwarding rule will delete these custom records. Doesn't make a lick of sense but I probably had 14 hours in this trying to figure it out and this finally worked. Support was no help here, just trial and error. I'm doing another test on a separate domain forwarding to the same site just adding the cname www record only "ext-sq.squarespace.com". As of now, that domain is working for root & www in safari and only www in chrome. Going to give it a few days to see if it starts working and will update my other domains if that is a better solution as there shouldn't be a records when you have a forwarding rule setup. I halfway get the www cname record. I'm doing this test because I noticed the cname record was the only record that was kept IF you had the default squarespace records loaded prior to setting up your forwarding rule. They just delete the a records which actually makes sense. I have verified the www cname record is not added if the squarespace default records were not previously in DNS prior to adding the rule. We'll see what happens with that test over the next couple of days. I'm also testing another domain with just the forwarding rule in place with no default cname & a records assigned. I'm betting it'll keep not working. I'm betting the other test with the www cname record will start working for root & www but will report back on that. Anyway, it will work for you if you just add those squarespace default records after applying your forwarding rule.