Docker is an awesome format for creating ultra efficient micro services for Synology NAS. In this video we are going to go over how to setup a Docker contain. # Synology DiskStation. The DiskStation by Synology (opens new window) is a famous NAS server solution for your home, allowing the installation of additional packages. We are proud to be able to provide an openHAB Synology package (opens new window). Status Page: The system will create a shortcut for the container’s status page in Docker. Web Page: Take Transmission for example, it has a WEB GUI for management. With this option, you can create a shortcut to easily access the interface. Enter the domain or IP address of your Synology NAS, followed by the local port set.
The other day I got fed up with having to insert diskstation.local:12345 to point towards an installed service on my NAS. I also thought that my SO has difficulties remembering all the ports (I do too) and cleaning up the browser cache doesn’t help either. So, I thought:
Wouldn’t it be nicer if instead of disksation.local:32400 I could just type plex.laurii.lan?
Yes! Yes, it would! :)
So I started my quest to make things happen.
My se case is the following:
As a local user, I want to have nice names for the services I’ve installed.
This breaks down into:
Since I don’t have WAN/VPN requirements, the closest solutios I could find were:
My solution is somewhat a hybrid of the two:
For the DNS server, I’ve installed Synology’s DNS Server package and enabled the DNS resolution as per most tutorials:
I then created a master zone named laurii.lan, with the DNS server pointing to the IP of the Synology machine:
I then created:
Once these are done, the DNS part is concluded. If you set up the DNS on your device (PC, phone etc.), typing something.laurii.lan will actually point back to your device:
Synology DSM provides you with the possibility to define reverse proxies via Control panel - Application portal. We can define a reverse proxy for plex:
Once saved, you can access the plex server as plex.laurii.lan. Nice!
Once we defined all servers, the Reverse proxy tab of the Application portal can look like this:
The idea is that now you can map any applications which expose ports to subdomains (eventually with their own defined ports).
Now, if you have a decent network, you already have a capable router and IMHO it’s better if you keep everything concentrated on the router. However, I thought that keeping the configuration local to my Synology box is worth the effort. Now when I install a new service, I only have to define a new reverse proxy to a subdomain.