Upgrading application - how to keep the DNS name?
Is there a way to have traffic for OLD and NEW IIS servers to use the same DNS name?
We have an application, FOO. Two IIS servers behind the F5, standard port 80 setup. It's an internal-facing application, not public access allowed.
The virtual server IP has a DNS hostname of FOO.company.com
We'd upgrading FOO to a new version, FOO version 2. We must run the original FOO while we migrate users to FOO 2. They'll be running parallel for a month in production, at least.
The application team, just this morning, said 'The server is now running IIS. Time for the F5!'
'So what do you want your new DNS name to be,' I replied.
'Can't we keep the old one? foo.company.com is pithy and the users like it.'
'Well, you know the F5 is not my primary job and I only know a little bit about it.'
Long faces all around.
'But,' I continued 'I'll see if there is a way to use 'foo.company.com' for both the old and new hosts.
So how about it? Two applications, two IIS hosts, one F5: one DNS name.
I'm aware that companies with non-captive users have this dilemma and THEY manage to do it. So why oh why can't I?