OldNuc wrote:Presently there is no DNS entry for the site. This is not unusual when a site is physically moved to a new host.
There are well-documented methods of avoiding downtime:
Cloudflare's DNS server makes this a trivial exercise. Define two A records, one for the "old" server and another for the "new" one. Requests will be served in a round-robin fashion. If you want to put more load on one server versus another, add multiple A records for the one you want to serve more requests. When I do this for HB, I make the "old" server read-only and prevent new logins so there's no need to resync the databases (assuming the database server is being migrated too).
Visitors cannot tell which server served their request. Of course, if the old server is denying logins, members who wish to post may notice, but they're a small subset of the site visitors. If I really mess up (e.g., I discover a serious bug in the new server post-switch), it's not hard to switch back, especially if you have both servers use a common database server.[Apologies for the geek-speak!]