How to set up a third-level domain on Windows Server + IIS with access to another server on the local network?

Question

Nginx

There is a home local network with a number of computers and devices (IP cameras, NAS servers). Virtual machines are running on two computers (A - 192.168.1.2 and B - 192.168.1.3):
- A:
- 192.168.1.21 - website/forum with CMS/CRM (LAMP);
- 192.168.1.22 - Home Assistant (LAMP) smart home server
- B:
- 192.168.1.31 - Windows Server + IIS + SQL + 1C - with forwarded port 80 from the router and access from the outside world via "white" IP and domain name , conditionally, HomeServer.com. Everything that is located on this server and published in the "inetpub" folder is available from outside by domain name.

Port-forwarding to other servers in the local area also works without problems, both by white IP and by domain name.

It is necessary to set up a 3rd level domain with access to local servers:
1) CRM.HomeServer.com - for 192.168.1.21
2) HA.HomeServer.com - for 192.168.1.22

Which way to dig? Googled that in IIS without using ngnix or Apache this cannot be done. Requires proxy modules. If you can get by with standard IIS tools, then how? If not, what specific modules will be needed and will Apache and/or ngnix be installed on Windows Server without conflicting with IIS? What other ways are there?

Answer 1

Proxy reverse