Bare bones domain migration
October 16, 2023 10:45AM
Hi,

We are undergoing a brand change.

I have an existing reverse proxy (not nginx):

https://foo.olddomain.com

Internally, the content is served off of port 8084.

but the company is moving to

https://new.newdomain.com

-- which will be running nginx and will have a new certificate from a new CA. But we would also like nginx to replace the old reverse proxy and have the new nginx instance also reverse proxy https://foo.olddomain.com -- at least until the domain is expired.

Both new.newdomain.com and foo.olddomain.com would connect to the same internal server on port 8084.

Obviously, the domain names and certificates would differ in the config file.

Is setting this up just a matter of having two server records? (Is there an example out there for this?)

Would a redirect be more appropriate?
Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 186
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready