I'm researching this utility/project on github called LANcache which is used for caching game downloads from the various online distribution methods such as Steam, Origin, Blizzard, etc. I'm fine with going through and setting up a dedicated system/VM to host this solution. What I'm unsure about is how does one configure the DNS side of things such that when an existing or new system plugs into my network like in the case of where I have a few people over for a LAN party that whenever people try to download and install a game that the DNS routes to this new LANcache system? Would I need to also create my own DNS server and route all my traffic through that via a config change on my router?
This website suggests this but I'm not 100% clear on it such that it would make things transparent to the systems on my network. They say "Remember to let you local DNS server forward all the required addresses to your nginx server.". This makes sense to me but it assumes I have my own DNS server (I guess)? Is this a case where I can setup my own DNS as primary and then use something like Google for the second and third or would my own DNS only just forward everything to different locations?
This website suggests this but I'm not 100% clear on it such that it would make things transparent to the systems on my network. They say "Remember to let you local DNS server forward all the required addresses to your nginx server.". This makes sense to me but it assumes I have my own DNS server (I guess)? Is this a case where I can setup my own DNS as primary and then use something like Google for the second and third or would my own DNS only just forward everything to different locations?