Asked by Spikeuk30
at 2024-07-20 13:42:28
Point:500 Replies:4 POST_ID:829042USER_ID:11947
Topic:
Microsoft IIS Web Server;Web Servers;Miscellaneous Networking
ok im moving some live websites to a new server. both HTTP sites and HTTPS port 80 /443
The client wont be able to make any dns A record changes until a few days later so I need to forward on requests from old webserver.
This is a Windows server 2008 / IIS7 webserver.
For example. www.test.com A-record points to 195.123.456.4
New web server has the website configured listening on 217.45.22.15
So I want requests going to 195.123.456.4 forwarding onto 217.45.22.15 seamlessly while still using the www.test.com url (without changing A-Record.)
I think this can be done with IP routing? BUT I have multiple other sites listening on port 80 on the same 195.123.456.4 IP address on the old webserver which need to remain there until a later date.
Any help would be greatly appreciated..
The client wont be able to make any dns A record changes until a few days later so I need to forward on requests from old webserver.
This is a Windows server 2008 / IIS7 webserver.
For example. www.test.com A-record points to 195.123.456.4
New web server has the website configured listening on 217.45.22.15
So I want requests going to 195.123.456.4 forwarding onto 217.45.22.15 seamlessly while still using the www.test.com url (without changing A-Record.)
I think this can be done with IP routing? BUT I have multiple other sites listening on port 80 on the same 195.123.456.4 IP address on the old webserver which need to remain there until a later date.
Any help would be greatly appreciated..
