Larklen

Wonder if anyone else is planning to use this on a Windows machine. I have one of my home servers set up using Windows 10 Pro and have taken a quick stab at getting this setup to no avail - doesn't seem to be too much in the way of guides/other people setting it up so I suppose I'll have to fiddle around with it. If anyone else has experience, I'd love to poke a brain or two!

I'd love to see a few pictures or video of how it looks at night without the sun glare! 

@thedude4bides You pretty much got the main use for it! That's mentioned on the github as well that its primarily for LAN events and for popular games, yeah most people will have it. One spot where is can shine though is, say there is an unexpected game that any number of people want to play, normally everyone would then need to download it from the Internet, since they didn't expect to play it at the event. With this set up, once one person downloads it from the internet, everyone else immediately pulls from the cache, so anyone who wants it after the one person downloaded it can grab it at the cache speeds.
 
@Norrah By default, this can be scaled down as far as you like  I set it up in my location (mainly just to try it out as an experiment) and the set up its on it an older computer hooked into a router, which then runs to a switch and then to several computers. No need for any fancy equipment as the magic is in the software itself, equipment just lets you reach higher speeds (which makes more of a difference especially if you already have a great internet connection, since you might already be getting ~25MBps for example).

I tried setting something like this up awhile ago, but couldn't get it to work properly. So I left it, until a new feature in Windows came out. The Windows Subsystem for Linux. So I tried the steps listed on the ArsTechnica website using the DIY method. And to my surprise it worked. After testing it some more. I then created a simple script to install bind9 and nginx, plus setting up all the need files. The scrtipt only works with networks with 24 bit subnet mask. You might want to test the performance difference between Linux and Windows. I attached the script for you to look at. Although I've only got Steam working.
steamcache.sh

I've got this working using the Windows Subsystem for Linux and using native windows exe of nginx and bind9. If you need any help setting this up, I'll be glad to help.

It should not be very difficult: Install docker and check if its working using https://docs.docker.com/docker-for-windows/#shared-drives then just edit the commands 
docker run \ --restart unless-stopped -d \ --name steam-cache \ -v {Path of Steamcache-cache-folder on the host drive}:/data/cache \ -v {Path of Steamcache-log-folder on the host drive}:/data/logs \ -p {Main IP for Steam Cache}:80:80 \ steamcache/generic:latest  
Adjust the other commands accordingly, you can configure multiple IPs by going into the Control Panel -- Network and Internet -- Network and Sharing Center -- Change adapter settings -- right click on your Network Interface and click on Properties -- select Internet Protocol Version 4 and choose use the following IP address -- enter your main IP of your system -- enter your preferred DNS-Servers -- click on andvanced to configure multiple IPs: just click add to add another one, if you don't know what to enter as Subnet mask just enter 255.255.255.0. As you said this is one of your Home Servers let the Steam Cache run on a different IP if you are already hosting another DNS Server or Webserver.
 
Additional note to the Path for the folders: You probably have to configure them in the docker application as a shared folder, but this should work in the newest version if your User has full access to the directories

I know this may sound like the typical questions for less tech-savy people, but: did you check docker with hello world and seriously: did you try turning it off and on again? and at last even if it is reporting as being restarted, just try to lookup any dns from that server by running "ipconfig/flushdns" and then "nslookup google.de 192.168.1.10". And i would stick using the local IPs and not 0.0.0.0 or at least use 127.0.0.1.
 
Oh and by the way what does "docker --version" say?

And it would help if you would post the command you used to start the steamcache-dns

Lets get this command a bit smaller:
docker run --restart unless-stopped -d --name steamcache-dns -p 192.168.1.10:53:53/udp -e UPSTREAM_DNS=1.1.1.1 -e STEAMCACHE_IP=192.168.1.11 -e BLIZZARDCACHE_IP=192.168.1.12 -e FRONTIERCACHE_IP=192.168.1.13 -e WINDOWSCACHE_IP=192.168.1.14 steamcache/steamcache-dns:latest goes to
 
docker run -f --name steamcache-dns -p 192.168.1.10:53:53/udp -e UPSTREAM_DNS=1.1.1.1 -e STEAMCACHE_IP=192.168.1.11 steamcache/steamcache-dns:latest
 
This should run the container in the foreground, thereby enabling console output. And we just remove the other services for now. Have you checked if you opened port 53 on your firewall?