Local Hostname Resolution To Port

How to Resolve a Local Hostname to a Port

Published on Friday, November 30, 2018

Adding friendly local URLs for services

How I setup mailhog to run in docker with exposed port 8025 to be accessible on http://mailhog and a local Gitea

This I adapted from the stackoverflow answer Using port number in Windows host file, there are a number of options proposed in answer to the question including using nginx or apache to act as a reverse proxy or running fiddler all the time to proxy the requests. I chose the netsh approach since we already make use of netsh so thought it would be good to understand it more and it is all built into Windows.

Setting up the local DNS

There are several way to do this, the quickest is probably just to add entries to the host file, another way is to install Unbound or if you are lucky enough to have a local Active Directory server you can configure it there (although that won't work while you are on other networks).

It is not possible to make this work on, however the entire block 127/8 is reserved for local loopback so any other 127.n.n.n address will work, more interesting reading about that on stackoverflow and in RFC 1700

Hosts file

Add a new entry for each service to the hosts file in C:\Windows\System32\drivers\etc\.       mailhog.internal       git.internal


Install Unbound.

Add entries to service.conf by default on Windows that is in C:\Program Files\Unbound

.local vs .localhost vs .test vs .internal

After reading round in circles about reserved TLDs such as rfc2606 which lists .test, .example, .invalid, .localhost as reserved domain names. This stackoverflow on best practices for internal domain and network names This TechNet article which goes back on previous advice about the use of .local and .internal.The risks of using my initial choice of .local due to possible clashes with mDNS and Zero Configuration Networking. Trying to use servicename.localhost with mixed results (works with hosts file but causes Unbound to throw and error and fail to start) and noticing that docker uses .internal I finally found RFC6762#appendix-G which lists .intranet., .internal., .private., .corp., .home. and .lan. as proposed reserved domain names, I settled on using .internal.

    local-data: "mailhog.internal A"
    local-data-ptr: " mailhog.internal"
    local-data: "git.internal A"
    local-data-ptr: " git.internal"

Restart the service to make sure the new settings are used.

Add at the top of the list of DNS servers in network settings.

Network settings with as DNS server

Add a netsh interface portproxy

netsh interface portproxy add v4tov4 listenport=80 listenaddress= connectport=8025 connectaddress=  
netsh interface portproxy add v4tov4 listenport=80 listenaddress= connectport=3005 connectaddress=

or by domain name

netsh interface portproxy add v4tov4 listenport=80 listenaddress=mailhog connectport=8025 connectaddress=  
netsh interface portproxy add v4tov4 listenport=80 listenaddress=git.local connectport=3005 connectaddress=

Between the 16 million loopback addresses and 65 thousand (48k usable according to TCP/IP number usage and the Microsoft article Port Exhaustion and You) ports that leaves us a whole lot of services we can address on a single machine.

I still need to figure out how this will work with IPv6 at the moment I only use IPv4 locally. I also need to understand the exact equivalence of and ::1/128.

netsh interface portproxy add v6tov4 listenport=80 listenaddress {IPv6Address | HostName} [connectaddress=] {IPv4Address | HostName} [[connectport=] {Integer | ServiceName}] [[listenaddress=] {IPv6Address | HostName} [[protocol=]tcp]

Full Network Shell (netsh) documentation on Microsoft docs.