Custom domain stuck on Cloudflare ownership verification and Error 1000 – retevox.ro

[mihaiciocau-source]

Hi Reflex team,

I’m having a custom domain issue with retevox.ro that appears to require investigation on the Reflex/Cloudflare side.

Current status:

• The root A record for retevox.ro points to 104.26.8.125, the routing IP provided by Reflex.
• The A record is set to DNS Only in Cloudflare.
• The certificate CNAME record is configured.
• The _cf-custom-hostname ownership TXT record is configured using the token generated by Reflex.
• Reflex now shows all three records — Ownership, Certificate and Routing — as Found.

However, domain verification remains stuck on:

“Waiting for Cloudflare to confirm ownership.”

Opening retevox.ro directly returns:

Cloudflare Error 1000 – DNS points to prohibited IP.

Earlier, Reflex also reported:

“Cloudflare refused this hostname: None of the A or AAAA records are owned by this account and the pre-generated ownership verification token was not found.”

I removed the domain from Reflex, added it again, and updated the ownership TXT record with the newly generated token. The previous ownership-token error disappeared and all three DNS records are now detected as Found, but the domain still does not activate and Error 1000 remains.

Reflex Build also performed a read-only check and confirmed that the public DNS records are present. It advised that this now warrants a Reflex infrastructure/support investigation rather than further DNS changes.

Could someone from the Reflex team please check:

1. Whether retevox.ro is correctly provisioned/activated as a custom hostname in the Reflex Cloudflare account.
2. Whether Cloudflare is reporting a rejection or pending ownership status for this hostname.
3. Whether 104.26.8.125 is still the correct routing target for this domain.
4. Whether the custom hostname needs to be reset or re-provisioned on the Reflex side.

I have not changed the DNS records further because Reflex currently detects all three required records as Found.

Thank you very much for your help.

[masenf]

issue has been addressed out of band yes?