We're moving our store to a new server with a new IP address and I'm trying to determine if there is a way to minimize the number of users who still "see" our old site during DNS propagation.
Right now, the plan is to put the old site in maintenance mode once we begin the migration so users will see a 503 message if they land on the old site.
Basically I'm trying to address this use case:
The server move is complete and we have updated the domain A record to the new IP address. Before the DNS change has completely propagated a user visits our site and is directed to the old server.
Is there any way to indicate that our site now lives at a new IP address for users who land on the old server? I know I could just redirect them by using the new IP address instead of the domain, but I would rather not use that solution if possible. Is there any way to indicate that
example.com should now map to
220.127.116.11 on the server level?
From other answers I've seen about dealing with DNS propagation, I suspect this is not possible. If this is not possible, I'm curious if there is a good reason for that. It seems like it would be useful for there to be a mechanism in place for a server to be able to tell a user that the domain they requested should now map to a different IP address.