Thank you - we’ve since discovered the person who invited me did not realize that “accounts” and “members” of accounts are not the same thing, and we are dealing with a sealevel.com domain entry on 3 separate accounts. Additionally, they made changes both in Cloudflare and on our domain registrar that I was not aware of when I made my post, and earlier replies today.
For clarification for anyone else going through this issue, since it was not made clear at all the difference between “accounts” and “members” of accounts, and that a domain can be added to more than one account.
My DKIM records did not work because the nameservers on our domain registrar pointed to the nameservers listed in the account for Person 1 (the original account). Person 1’s account has the correct DNS records, and is where I should have been adding the new DKIM record.
Person 2 created their account at some point in the past, after being invited to Person 1’s account - when Person 2 created their account, they also added sealevel.com, which created a duplicate which had different nameservers (the Issac and Zainab entries). However, none of their DNS records took effect since the nameservers in the domain registrar still pointed to Person 1’s account.
Yesterday, Person 2 invited me to their account, which when I joined also created a new account. There was nothing that told me a sealevel.com domain entry existed under another account - I came into a blank domain page, so I added sealevel.com, which had a third set of nameservers. I worked yesterday on the DKIM records under this account and didn’t understand why they weren’t working, and made my original post. I afterwards saw the difference in the nameservers listed in our domain registrar (pointing to what was listed in Person 1’s Cloudflare account) and the nameservers listed for sealevel.com under my Cloudflare account.
Overnight, Person 2 activated the sealevel.com in their account. They then changed the nameservers in our domain registrar to what is listed in their Cloudflare account (the Issac and Zainab entries). This then broke our website.
Earlier this morning, I was unable to change the nameservers back to their original settings in the domain registrar - they told me it was locked due to propagation. However, after escalation I was able to get the domain registrar to revert the nameservers there back to the original settings (the James and Pricilla entries), which now points to Person 1’s DNS records on Cloudflare. I am deleting the sealevel.com domain from Person 2 and my accounts to avoid further issues.
Thanks to everyone for all the help. This could have been avoided with better understanding that 1.) each person should have been added as a member to the existing account of Person 1, and 2.) that domains can be added to multiple accounts, which should be avoided.
