Is there such thing as internal "domains"
Is there such thing as internal "domains"
Absolutely, if your computers aren’t always active, installing a Pi and using Pi-hole makes the most sense. You wouldn’t want to constantly manage DNS across an entire network on a machine that’s not always online. A Pi would probably save you money by reducing electricity use when it’s not needed.
As brwainer mentioned, DNS-based options won’t work here. Pi-hole won’t help because it will redirect all traffic to the same IP addresses, like http://teamcity.jdturing.com and http://octops.jdturning.com. The choice of port depends on your application—usually 80 for browsers. You should set up an HTTP proxy on the server hosting everything, then configure virtual hosts to map to different subdomains. I’m not sure if ISS supports this, but Apache and nginx do. Check their documentation on virtual hosts and reverse proxies. Another approach is to create separate virtual network interfaces, assign unique IPs to each, and bind your web services to those IPs. I don’t know how to implement this with Windows or ISS, though I’ve done it successfully with GNU/Linux and nginx before.