SSL Certificate Issue for new Custom Domain

Hello,

Last week I registered the domain networkvoice.org (Club 4652) in the desire to use it as the domain for our free toast host web site. I created the two A and MX records I found in the forums and was able to save successfully on the admin panel. Requests to the page work, but the SSL certificate being returned to the browser is the wildcard toastmastersclubs.org certificate. From browsing the forums, it seems that an SSL cert is automatically generated by FTH and applied. It makes sense since I don't see a lot of talk about generating a CSR to get my own cert.

How long does it take to get the cert via FTH? Is it automatic or do I need to request it or... Just checking.

Cheers,
Stefano

The MX records are not correct
remove
networkvoice.org.    3600    IN    MX    5 alt2.aspmx.l.google.com.
networkvoice.org.    3600    IN    MX    5 alt1.aspmx.l.google.com.
networkvoice.org.    3600    IN    MX    10 alt3.aspmx.l.google.com.
networkvoice.org.    3600    IN    MX    10 alt4.aspmx.l.google.com.
networkvoice.org.    3600    IN    MX    1 aspmx.l.google.com.

add

networkvoice.org.    3600    IN    MX mail.networkvoice.org

I have corrected the cert issue
www.networkvoice.org/ is working

Hey Brian,

Thanks for the quick response. I missed those records. Those are the default for Google Workspace. I took those out. I had to think through if I wanted to use those mailboxes for email handling, but figured I'd have the club members stick to what they used to use. Can you suggest SPF and DKIM  (and DMARC) records I should publish? 

Also, the MX record you suggested should now be visible. It was there, but likely overridden by the Google stuff.

Thanks again!
Stefano

You shouldn't need SPF or DKIM records as your domain will not send any email.

Hey Brian,

Ah OK. All the officer emails other login notifications will still come from the same old place? Cool. That works.

Thanks Brian!

Stefano