I posted this threat last month and it just happens its exactly 1 month ago.
The DNS record for my root disappeared, and I needed to create a new record.
I checked the audit logs, and outside of the record, add log from today again today 5/7 (last time 4/7, I only see logs for add/remove of SSL certificates going back several weeks. The secondary record for www was still in tack.
Cloudflare is my registrar for [domain]
Current setup for records CNAME cpf-coaching com to my Cloudflare page CNAME www to my Cloudflare page
Previous setup for records CNAME @ to my Cloudflare page
Last month someone mentioned that they couldn’t access might sight, which prompted me to discover this. Now it’s happened again. I am unsure if it is part of the DNS flattening since I don’t have an IP for the Cloudflare pages site. Any recommendations?
Are you asking about the lack of any record named @? You will never see any record displaying the name @ in Cloudlfare. @ is just a representation of your apex name. Once you enter it and save the record, it will be shown as the apex name, example.com.
@epic.network I have been having something [similar with root domain not working while www-domain works](https://community.cloudflare.com/t/dns-record-disappears-again/506427?u=christophefoulon)
When I set up the records, it tells me, CNAME records normally can not be on the zone apex. We use CNAME flattening to make it possible. [Learn more](https://developers.cloudflare.com/dns/additional-options/cname-flattening/) With my account type, CNAMEFlattening is required.
Do you think I should resolve this with a redirect?
It is preferable to pick one name as the canonical name and redirect to it. While I would use the new Redirect Rules rather than Page Rules, these Community Tutorial topics cover the concept.
I tried using both Page Rules and Redirect Rules.
I opted to root to the www version, swapping around the root to the Cloudflare page in the DNS section and adding www to the dummy IP.
Fingers crossed, this is a long-term fix/patch/solution.