You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue Description:
I think that this issue is different than the others as the other posts seem to be related to not resolving certain domains, but mine won't resolve any to the local server - it just returns the real servers IP ... even cs.steampowered.com
My DNS settings are set (and checked) to only use 192.168.254.1 (the steamcache-dns)
I have run ipconfig /flushdns
I have tried with and without setting UPSTREAM_DNS
Any ideas? Thanks
Docker Container Output:
Setting up steam -> 192.168.254.2
...
10-Nov-2018 11:04:36.624 zone cs.steampowered.com/IN: loaded serial 2018111004
The text was updated successfully, but these errors were encountered:
The problem is that your server list is not complete...
It doesn't list Australian servers,
If I change my servers to the UK it works...
Not good for LANs though, since people have to manually set it to use UK or US over here.
Do you have a list of domains that are not listed for your region? If you do you can create a PR over at https://github.com/uklans/cache-domains and they will automatically get pulled by the DNS image at startup.
If we don't have a list of domains to add, we are unable to add them in.
Closing as inactive, plus due to new built in steam support - see lancachenet/monolithic#85 - Steam should now redirect correctly to cache regardless of location.
Issue Description:
I think that this issue is different than the others as the other posts seem to be related to not resolving certain domains, but mine won't resolve any to the local server - it just returns the real servers IP ... even cs.steampowered.com
My DNS settings are set (and checked) to only use 192.168.254.1 (the steamcache-dns)
I have run ipconfig /flushdns
I have tried with and without setting UPSTREAM_DNS
Any ideas? Thanks
Docker Container Output:
The text was updated successfully, but these errors were encountered: