Is there such thing as internal "domains"
Is there such thing as internal "domains"
Hi, I see you're looking for ways to share your services through a single domain instead of individual URLs. That’s a common goal for simplifying access and management. You mentioned using Windows 10 Enterprise LTSB and having multiple software running on different ports. It sounds like you might be interested in consolidating your hosting setup. I can help you explore options like setting up a reverse proxy, configuring DNS records, or using a domain-based service gateway. Let me know which services you're targeting and what tools you have available, and we can walk through the steps together.
Consider setting up a DNS forwarder or resolver that maps those domain names to an internal IP on your local network. This way, it can handle DNS queries and deliver the correct local address to clients. This functionality is similar to what advanced firewalls like PfSense provide.
If it's a bit challenging, you can also modify the hosts file to connect the domain name with the IP address.
I'll try it out. Installing a DNS server in Windows seems straightforward, just figure out how to register specific URLs so the system recognizes their local addresses. Thanks. I understand this could work, but applying the hosts file on every machine would be tedious. I’ll go with the local resolver and see how it performs—maybe some research is needed, but it shouldn’t be too hard.
You'll encounter a problem because a DNS name just gives the browser the IP address, not the port number. There are special DNS entries called services that include port details, and some platforms like Minecraft support these, but web browsers don't.
It seems like you're anticipating a challenge with DNS resolution. I'm hoping once the DNS resolver is active, you'll be able to update the URLs for TeamCity and Octopus to the specified subdomains (without specifying ports), and that change will be recognized. Good luck!
There are several approaches to achieve this. I’ll share a few methods I’ve tried before. You can change the hosts file on all devices in your network so they’re reachable by hostname instead of IP. For Linux, place the file in `/etc/hosts`, and for Windows, keep it in `C:\Windows\System32\drivers\etc`. On Linux systems, install dnsmasq to act as your DNS server. You can configure DNS on either your router or individual computers. Just edit the appropriate hosts file to map hostnames to IP addresses. On a Linux machine or Raspberry Pi, add pi-hole as your DNS server. It uses dnsmasq but also blocks ads. Once installed, update `/etc/hosts` to link hostnames with IPs. If you want more control, run pi-hole inside a Docker container. Among these options, I’m currently using the last one—deploying pi-hole via Docker on Windows. I think you can still do this on Windows using Docker as well.
Docker is gaining attention for good reasons—it’s worth checking out and possibly adopting.
Another suggestion: Have you come across PiHole? It’s built for Raspberry Pi or any Linux system and it blocks ads on your network right away, before the data even arrives. This can ease congestion when many users browse online. The point is that PiHole can also handle local hostnames if you modify the /etc/hosts file.
Your `docker-compose.yml` file is the setup you used to launch pi-hole on your CentOS machine. The extra-host settings instruct Docker to update hostname-to-IP mappings in `/etc/hosts`. The configuration includes IP ranges, DNS entries, and proxy details for managing domain resolution. Adjust the placeholder values as needed for your environment.