dns not resolving to upstream
stelar7 opened this issue · comments
Issue Description:
I have set lancache-dns as the upstream dns on my router, and for some reason it is unable to resolve any cached domains. (Other domains work fine).
The server where the container is can ping both cached, and uncached domains. But the machines running behind the router can only see the uncached domains.
I am not sure if this would be an issue with monolithic or not, so Im posting this here in hopes of help.
Docker Run Command:
export HOST_IP=`hostname -I | cut -d' ' -f1`
docker run --restart unless-stopped --name lancache-dns --detach -p 53:53/udp -e USE_GENERIC_CACHE=true -e LANCACHE_IP=$HOST_IP -e UPSTREAM_DNS="8.8.8.8" lancachenet/lancache-dns:latest
docker run --restart unless-stopped --name lancache --detach -v /cache/data:/data/cache -v /cache/logs:/data/logs -p 80:80 lancachenet/monolithic:latest
docker run --restart unless-stopped --name sniproxy --detach -p 443:443 lancachenet/sniproxy:latest
echo Please configure your router/dhcp server to serve dns as $HOST_IP
Docker Container Output:
monolithic log can be found here: https://gist.github.com/stelar7/3fa24dc8a0224c12f00827e3bad03ddd
Executing hook /hooks/entrypoint-pre.d/10_generate_config.sh
/opt/cache-domains /scripts
HEAD is now at 5ab391a Domain correction for Riot's new chunking patcher (#105)
/scripts
_ _ _
| | | | | |
___| |_ ___ __ _ _ __ ___ ___ __ _ ___| |__ ___ _ __ ___| |_
/ __| __/ _ \/ _` | '_ ` _ \ / __/ _` |/ __| '_ \ / _ \ | '_ \ / _ \ __|
\__ \ || __/ (_| | | | | | | (_| (_| | (__| | | | __/_| | | | __/ |_
|___/\__\___|\__,_|_| |_| |_|\___\__,_|\___|_| |_|\___(_)_| |_|\___|\__|
configuring /etc/resolv.conf to stop from looping to ourself
Bootstrapping DNS from https://github.com/uklans/cache-domains.git
----------------------------------------------------------------------
Using Generic Server: 192.168.1.156
Make sure you are using a monolithic cache or load balancer at 192.168.1.156
----------------------------------------------------------------------
Processing service: apple
Enabling service with ip(s): 192.168.1.156
Processing service: arenanet
Enabling service with ip(s): 192.168.1.156
Processing service: blizzard
Enabling service with ip(s): 192.168.1.156
Processing service: daybreak
Enabling service with ip(s): 192.168.1.156
Processing service: epicgames
Enabling service with ip(s): 192.168.1.156
Processing service: frontier
Enabling service with ip(s): 192.168.1.156
Processing service: hirez
Enabling service with ip(s): 192.168.1.156
Processing service: nexusmods
Enabling service with ip(s): 192.168.1.156
Processing service: neverwinter
Enabling service with ip(s): 192.168.1.156
Processing service: nintendo
Enabling service with ip(s): 192.168.1.156
Processing service: renegadex
Enabling service with ip(s): 192.168.1.156
Processing service: riot
Enabling service with ip(s): 192.168.1.156
Processing service: rockstar
Enabling service with ip(s): 192.168.1.156
Processing service: sony
Enabling service with ip(s): 192.168.1.156
Processing service: steam
Enabling service with ip(s): 192.168.1.156
Processing service: uplay
Enabling service with ip(s): 192.168.1.156
Processing service: teso
Enabling service with ip(s): 192.168.1.156
Processing service: twitch
Enabling service with ip(s): 192.168.1.156
Processing service: warframe
Enabling service with ip(s): 192.168.1.156
Processing service: wargaming
Enabling service with ip(s): 192.168.1.156
Processing service: wsus
Enabling service with ip(s): 192.168.1.156
Processing service: xboxlive
Enabling service with ip(s): 192.168.1.156
---
finished bootstrapping.
Executing hook /hooks/supervisord-pre.d/10_config_check.sh
checking Bind9 config
2019-09-28 10:47:30,178 CRIT Set uid to user 0
Aight, turns out i just set the DNS server in the wrong place.. RIP