search

lancachenet / lancache-dns

DNS Docker service for a lancache.
https://hub.docker.com/r/lancachenet/lancache-dns/
MIT License
285 stars 75 forks source link

Steamcache doesn't appear to be resolving #80

Closed BurningTheSky closed 4 years ago

BurningTheSky commented 5 years ago

Issue Description: When I do a nslookup against the cache IP it doesn't resolve. I can see a couple of errors in the log but I am not sure how to deal with them.

Docker Run Command: docker run --restart unless-stopped --name steamcache-dns --detach -p 192.168.0.80:53:53/udp -e USE_GENERIC_CACHE=true -e LANCACHE_IP="192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84" steamcache/steamcache-dns:latest

Docker Container Output:

$ docker logs 8ca8b1d2b93e

| |                                    | |                     | |

| | _ _ _ | |_ | | / | / \/ ` | ' _ \ / __/ _ |/ | ' \ / \ | ' \ / \ | __ \ || / (| | | | | | | (| (| | (| | | | /| | | | / |_ |/__|_,|| || ||_\,|_|| ||_()| |_|_|\|

Bootstrapping DNS from https://github.com/uklans/cache-domains

Using Generic Server: 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Make sure you are using a monolithic cache or load balancer at 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84

/scripts/bootstrap.sh: line 30: [: too many arguments Processing service: apple Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: arenanet Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: blizzard Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: daybreak Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: frontier Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: hirez Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: nexusmods Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: nintendo Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: origin Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: renegadex Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: riot Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: rockstar Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: sony Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: steam Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: uplay Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: twitch Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: wargaming Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: wsus Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84 Processing service: xboxlive Enabling service with ip(s): 192.168.0.81 192.168.0.82 192.168.0.83 192.168.0.84

finished bootstrapping.

checking Bind9 config Running Bind9 tail: can't open '/var/log/named/general.log': No such file or directory tail: can't open '/var/log/named/default.log': No such file or directory tail: can't open '/var/log/named/queries.log': No such file or directory

==> /var/log/named/general.log <== 20-Apr-2019 15:42:28.845 all zones loaded 20-Apr-2019 15:42:28.847 running 20-Apr-2019 15:42:28.847 rpz: rpz: reload start 20-Apr-2019 15:42:28.847 rpz: rpz: reload done tail: /var/log/named/general.log has appeared; following end of new file tail: /var/log/named/default.log has appeared; following end of new file

==> /var/log/named/default.log <== 20-Apr-2019 15:42:28.836 managed-keys-zone: loaded serial 0 20-Apr-2019 15:42:28.843 zone rpz/IN: loaded serial 2 20-Apr-2019 15:42:28.845 zone cache.steamcache.net/IN: loaded serial 1555774944 tail: /var/log/named/queries.log has appeared; following end of new file

==> /var/log/named/queries.log <== 20-Apr-2019 15:42:45.583 client @0x564b48304e40 192.168.0.30#57747 (content1.steampowered.com.fenris.local): query: content1.steampowered.com.fenris.local IN A + (172.17.0.4)

==> /var/log/named/default.log <== 20-Apr-2019 15:42:46.440 client @0x564b48304e40 192.168.0.30#57747 (content1.steampowered.com.fenris.local): query failed (SERVFAIL) for content1.steampowered.com.fenris.local/IN/A at query.c:10644 20-Apr-2019 15:42:46.790 client @0x564b48296760 192.168.0.30#57748 (content1.steampowered.com.fenris.local): query failed (SERVFAIL) for content1.steampowered.com.fenris.local/IN/AAAA at query.c:10644

==> /var/log/named/queries.log <== 20-Apr-2019 15:42:46.441 client @0x564b48296760 192.168.0.30#57748 (content1.steampowered.com.fenris.local): query: content1.steampowered.com.fenris.local IN AAAA + (172.17.0.4) 20-Apr-2019 15:42:46.791 client @0x564b48304e40 192.168.0.30#57749 (content1.steampowered.com): query: content1.steampowered.com IN A + (172.17.0.4)

==> /var/log/named/default.log <== 20-Apr-2019 15:42:47.475 client @0x564b48304e40 192.168.0.30#57749 (content1.steampowered.com): query failed (SERVFAIL) for content1.steampowered.com/IN/A at query.c:10644 20-Apr-2019 15:42:47.632 client @0x564b48296760 192.168.0.30#57750 (content1.steampowered.com): query failed (SERVFAIL) for content1.steampowered.com/IN/AAAA at query.c:10644

==> /var/log/named/queries.log <== 20-Apr-2019 15:42:47.476 client @0x564b48296760 192.168.0.30#57750 (content1.steampowered.com): query: content1.steampowered.com IN AAAA + (172.17.0.4)

BurningTheSky commented 5 years ago

monolithic config is: docker run --restart unless-stopped --name lancache --detach -v /cache/data:/data/cache -v /cache/logs:/data/logs -p 80:80 -e CACHE_MEM_SIZE=4000m -e CACHE_DISK_SIZE=1000g steamcache/monolithic:latest

ip addr: 2: ens160: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:50:56:b7:c5:10 brd ff:ff:ff:ff:ff:ff inet 192.168.0.29/24 brd 192.168.0.255 scope global ens160 valid_lft forever preferred_lft forever inet 192.168.0.80/24 brd 192.168.0.255 scope global secondary ens160 valid_lft forever preferred_lft forever inet 192.168.0.81/24 brd 192.168.0.255 scope global secondary ens160 valid_lft forever preferred_lft forever inet 192.168.0.82/24 brd 192.168.0.255 scope global secondary ens160 valid_lft forever preferred_lft forever inet 192.168.0.83/24 brd 192.168.0.255 scope global secondary ens160 valid_lft forever preferred_lft forever inet 192.168.0.84/24 brd 192.168.0.255 scope global secondary ens160 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:feb7:c510/64 scope link valid_lft forever preferred_lft forever

alantreadway commented 5 years ago

Had the same issue this morning, I recreated the container but specified UPSTREAM_DNS too and everything seems to have started working.

-e UPSTREAM_DNS=1.1.1.1

Edit: To clarify - in my case, queries for www.amazon.co.uk and other popular TLDs were resulting in SERVFAIL responses, just noticed that the OPs messages were about domains that should be redirected to the LANCACHE_IP, so perhaps a different problem?

BurningTheSky commented 5 years ago

Funny you should mention that, that is exactly what I did about a hour ago and it appears to have fixed my issue. I wonder if the default config isn't entering anything?

alantreadway commented 5 years ago

I only set up steamcache-dns for the first time this week, so my assumption was that the Docker image had changed; however the Docker Hub entry doesn't indicate any change in the published image in two months: https://hub.docker.com/r/steamcache/steamcache-dns/tags

My container did get restarted overnight (the Unraid host rebooted), so my guess is something might be screwy with the dynamic part of the bootstrap for starting the container (e.g. building Bind9 config from https://github.com/uklans/cache-domains) which results in a config without a valid upstream DNS configuration - perhaps because of a change in https://github.com/uklans/cache-domains?

VibroAxe commented 5 years ago

This was an issue with giving multiple LANCACHE_IPS, should be fixed in latest?

unspec commented 4 years ago

Closing due to inactivity. Feel free to reopen if you still need some help.