Resetting our domain

Philip Wilson

• February 10, 2026 01:05

Our custom domain was attached while a root AAAA record still existed.
DNS is now correct (A record + www CNAME only).
The site works on a Brizy subdomain, but the custom domain continues to serve old hosting content.
The new Brizy Cloud UI does not allow removing/detaching the domain.

Please reset / detach the domain on your side so it can be re-verified and bound correctly.

This is in regards to our website www.engageinternational.org
34.237.47.210

 

Many thanks,

 

0

• 

  KC George

  • February 10, 2026 07:13

  Hello Philip,

  The A Record and the CNAME record you have added are still being propagated. In most locations, the A Record continues to show the IP: 43.250.142.25. Let's check the propagation status again tomorrow. Once the correct details show up for the A and CNAME records, we will fix the custom domain issue.  

   

  

   

  0
• 

  Philip Wilson

  • February 15, 2026 04:32

  Hello,

  DNS is correctly resolving to 34.237.47.210.

  Authoritative nameservers respond correctly.

  However, HTTPS returns ERR_SSL_PROTOCOL_ERROR.

  The Brizy subdomain redirects to the custom domain, indicating the custom domain is active.

  SSL likely failed during initial validation when DNS was not yet resolving.

  Please:

  1. Remove the custom domain binding completely.

  2. Clear any existing SSL certificate state.

  3. Re-issue SSL for:
     engageinternational.org
     www.engageinternational.org

  Thank you.

  0
• 

  KC George

  • February 16, 2026 04:32

  Hello Philip,

  Yes; the A Record is now pointing to the correct IP address. Your CNAME record needs a correction. Once you make the correction, kindly get back to us. We will fix the SSL certificaet for you. 

  

      

  0

Please sign in to leave a comment.