Manged Wordpress - allow primary domain changes without DNS check
Can you consider allowing us to change the primary domain without checking to see if the A record points to the IP address first?
Doing so would allow us to use firewall services like sucuri or to test out the new host by editing our host files.
Also, it prevents the short amount of downtime while the A record points to the new server but the certificate is not setup etc..
We are currently looking at ways to improve upon domain changes and appreciate you sharing your feedback about how this impacts you so we can make sure it’s considered as we go forward.
Steve Simons commented
This is a major limitation.
It's a really big deal especially if you're wanting to migrate existing sites. There is no way you can migrate an existing site to MWP without downtime, something that is almost never a limitation anywhere else (example LW Cloud Sites).
It makes it impossible to just edit your hosts file and truly test a site, as many licenses (fonts, plugins, chat services, etc.) are keyed to the site name and other integrations (SSO, etc.) expect a referrer from or are configured to redirect to the real site name. A testing url/sitename simply isn't a viable solution for test many sites anymore.
I'm guessing this limitation might be because the SSL certificate issuing process requires an http challenge, which isn't available to the platform until the dns is updated. Provide support for DNS challenges, or option to upload our own SSL certificate (which would be another stand-alone Vote Yes item), or even using temporarily a self-signed certificate would be better than the current solution.
Barry Tuber commented
This has been an issue for me as I migrate sites into the Managed WP environment, especially for certain domain registrars that seem to propogate their changes more slowly than others (Network Solutions). It would be nice to be able to have this work more smoothly and the fact that this was raised as an issue a year ago and it is still sitting out there is concerning.
I cannot recommend Managed WP hosting from LiquidWeb to any of my clients until this gets fixed. I can't tell them I have to break their website to launch it when there's no reason for it.
Barry McKay commented
I agree, in addition, obtaining new clients with busy popular sites becomes difficult as you must take their site down to migrate them in and live. Then you must trust that the rename will work, or scramble to fix things after the site has gone live.
A viable option would be to hook in the DNS TXT record validation for Let's Encrypt, and make renaming a multi-step process:
1) Issue rename request through MWP Control Panel, receive a DNS TXT record to add.
2) Display a button to validate record in the MWP control panel, or periodically try.
3) Once validated, proceed with SSL installation and rename.
I know there is a lot to those 3 steps which I just trivialized, but it would solve the problem.