We are moving IIS webservers and sql servers....
In order to avoid the client updating the A-record at stupid-o-clock we wanted to redirect users to the new webserver automatically and seamlessly..
points to 184.108.40.206 on webserver A.
we have a new webserver B with an instance of test.com running 220.127.116.11
On webserver A I created a IIS reverse proxy rewrite rule to redirect 18.104.22.168 to 22.214.171.124 inbound and outbound.
It seemed to work, but then realised parts were not being redirected. It seemed to be using the web.config file on server A but using content from server B.
Because the web.config file was in use the old sql server on A was being used and not the new one on B.
How can I redirect all requests to the site to B and then replies back to A.
I basically want a seamless experience - forwarding everything on to the new webserver not using the web.config on the old server....................
and defintly not the old sql server.
I cant configure routing policies at a firewall level as we don't have access to the router its a shared office etc.