How to test

• Configure a separate machine to use the cache server as a DNS server.

• Flush the DNS cache (use ipconfig /flushdns on Windows)

• Run a DNS lookup of an address that isn't to be cached using nslookup (Windows example):

  C:\Users\Ryan> nslookup google.ca
  Server:  UnKnown
  Address:  192.168.100.205
  
  Non-authoritative answer:
  Name:    google.ca
  Addresses:  2607:f8b0:400b:80e::2003
            172.217.0.99
  

  You should see your cache server IP listed as the DNS server being queried, followed by the real google.ca IP. This indicates that Dnsmasq is able to pass DNS requests through without redirecting traffic.

• Run a DNS lookup of an address that is to be cached using nslookup (Windows example):

  C:\Users\Ryan> nslookup steamcontent.com
  Server:  UnKnown
  Address:  192.168.100.205
  
  Name:    steamcontent.com
  Address:  192.168.100.205
  

  You should see your cache server IP listed twice this time. This indicates that Dnsmasq is found steamcontent.com in its list of addresses to redirect, and your cache server IP will be used as the steamcontent.com IP.

• Test caching by downloading a game and watching the logs and cache directories:

  • Use ll data/logs/ repeatedly from the cache machine to check if the logs are filling up. You should see sizes increase as traffic is handled.
  • Use du -h -d 1 data/cache repeatedly from the cache machine to see the size of each cache.
  • If you don't see anything being logged or cached, then most likely the service uses HTTPS and is being passed-through SNI Proxy instead. It could also be that the addresses for the service aren't setup correctly in the conf files.

• Uninstall and redownload the game. You should see it download much quicker this time, without much (if any) internet traffic.