TOPIC:

Is there an FTH recipe or checklist for changing a club's name along with changing it's custom domain? I haven't found anything directly on-point in my forum searches.

I've got the documentation for setting up the DNS records with the new domain and changing the domain in the FTH basic settings. I can also figure out many of the user text changes on the website.

I'm worried about the secret stuff. Obviously, I'd rather learn from somebody else's knowledge & experience than from my own errors.

For example, do I need to rip out the DNS records pointing to FTH for the old to-be-abandoned domain before setting up the new one? And, do I need to wait for the deletions to propagate before adding the DNS records to the new domain?

Can you point me in the right direction?

Thanks in advance,

K

See support.toastmastersclubs.org/doc/item/d...tical-considerations

While you can certainly set up two custom domain names at your registrar to point to the FTH server, that will not really work on our end because you can only put one of them in the database.

FTH needs to know what your domain name is so that it can search for it to find your website data when you access your website using your custom domain name--that is why you enter it in the admin console. Since the database only supports searching for one domain name to find your website, having two domain names registered and configured to point to the FTH server will not work for both. Only the domain name that is in the database will work.

My new custom domain is bringing up the "Request a Website" page www.toastmastersclubs.org/welcome/?qCWm

I put in the needed DNS records in the new domain. Refer to the screenshot of the DNS via GoDaddy.



Also, I changed the basic settings in FTH to show the new domain: www.tysonsregionaltoastmasters.org Since the old domain is down I can't easily verify the new setting for an error ... but that's my suspicion.

Can you help?

Ken Portnoy
CPRES, Tysons Regional Toastmasters
Club #01269860




Since the old domain is down I can't get back into the basic settings to check for a typo. That's my current hypothesis.

Your club number address will always work.
1269860.toastmastersclubs.org/

Thanks for the response. I got into the website. The setting was wrong!

Next: The changed custom domain fails to save. I tried both Chrome and Edge just in case it was a Chrome thing. Same message. The first is Chrome. The second is Edge.



Oddly I received the domain name change confirmation although it doesn't seem to stick.


Thx!!!!

portnoyk: I was able to update the domain setting in the admin console. The new domain is now associated with your website, and the old domain no longer works for your website.

Brian (and others): Because adding a domain name causes background processes to run related to producing a HTTPS cert ... this takes a bit of time and removing an old domain (and ditching the old cert) takes a bit of time. Occasionally, when changing domains, it may be better to delete the first domain, save, wait a minute, and then enter the new domain and save. This ensures that the system has sufficient time to process the change. This is what I did in this case.

Thanks for your intervention to move this forward although I've still got issues:

1) While the basic setting now seems correct, the FTH welcome site is still coming up instead of the club site in response to www.tysonsregionaltoastmasters.org The site viewdns.info is showing the right URL for both the domain and the www subdomain. Should I toss this problem at GoDaddy or do you think it might be at your end.

2) The club email addresses are showing as (officer)-1269860@toastmastersclubs.org Will email addressed to (officer)@tysonsregionaltoastmasters.org be handled properly? Will the email address display change? Is this a symptom of an incomplete conversion to the new custom domain?

1) clear your browser cache your site is coming up correctly www.tysonsregionaltoastmasters.org/

2) the email addresses show with the domain you access the site with, it is working as it is supposed to.

As Brian is pointing to, browsers cache redirects... We use a redirect to send you to the welcome page--your browser is remembering that and reusing it even if it no longer needs to.

You can either clear your cache as Brian notes or just put a ?1 (any number will work) on the end of the url to kill the redirect until your browser figures out that the redirect is no longer valid.