Re: [hlds_linux] SteamCMD FQDNs and/or IP addresses Escaped Turkey -
I setup some logging on the "bind" instance I use for name- resolution on the same Debian installation that happens to host my TF2 servers, and then forced an SteamCMD update on one of them. That resulted in the following stuff (sanitized copy included further below) in the logs for "bind". Hopefully, that was kind-of what you were originally looking-for. Some of it is probably generated from the SourceMod auto- update feature, and I use the SourceMod plug-in for Steam- Community integration, but other than that I would assume anything with "Steam" in the FQDN is requested by either SteamCMD or SRCDS itself. - Weasel 12-Jun-2013 19:57:09.390 queries: info: client 127.0.0.1#48360: query: steamcommunity.com IN A + (127.0.0.1) 12-Jun-2013 19:57:09.390 queries: info: client 127.0.0.1#48360: query: steamcommunity.com IN AAAA + (127.0.0.1) 12-Jun-2013 19:59:52.607 queries: info: client 127.0.0.1#55587: query: client-download.steampowered.com IN A + (127.0.0.1) 12-Jun-2013 19:59:52.864 queries: info: client 127.0.0.1#43033: query: media.steampowered.com IN A + (127.0.0.1) 12-Jun-2013 19:59:56.777 queries: info: client 127.0.0.1#40900: query: crash.steampowered.com IN A + (127.0.0.1) 12-Jun-2013 19:59:56.777 queries: info: client 127.0.0.1#40900: query: crash.steampowered.com IN AAAA + (127.0.0.1) 12-Jun-2013 20:00:33.931 queries: info: client 127.0.0.1#36706: query: update.sourcemod.net IN A + (127.0.0.1) 12-Jun-2013 20:00:33.932 queries: info: client 127.0.0.1#36706: query: update.sourcemod.net IN AAAA + (127.0.0.1) _________________________________________________ Back on topic: All I want to know are the FQDN or IP addresses to exclusively allow SteamCMD access. I prefer to block as much as possible and only open what is needed; knowledge is power. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
