How to test

• Point a single machine to the caching server by setting its network config to use the caching server IP for DNS.

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

• Test DNS using nslookup (Windows example):

  C:\Users\Ryan> nslookup steampowered.com
  Server:  UnKnown
  Address:  192.168.100.205
  
  Non-authoritative answer:
  Name:    steampowered.com
  Address:  96.7.203.235
  

  You should see your caching server IP followed by the steampowered.com IP. The caching machine handles the DNS request but does not cache that URL so the original IP is returned.

  C:\Users\Ryan> nslookup steamcache.cs.steampowered.com
  Server:  UnKnown
  Address:  192.168.100.205
  
  Name:    steamcache.cs.steampowered.com
  Address:  192.168.100.205
  

  You should see your caching server IP listed twice this time. The caching machine handles the DNS request as well as the caching that URL, so the caching machine IP is returned.

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

  • Use ll data/logs/ repeatedly from the caching 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 caching machine to see the actual size of each cache.
  • If you don't see anything being logged or cached, then most likely the service uses SSL and is being passed-through sniproxy and not cached, or the URLs 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.