Jameszy

Members
  • Posts

    1
  • Joined

  • Last visited

Everything posted by Jameszy

  1. Edit: Problem Solved. Changed interface from br0 to Bridge to share the same ip address as the unraid machine, added port forwarding for port 80 container side to 81 host side... Service still accessible from the LAN, service accessible from unraid... BOOM works! Greetings! I have installed the adguard docker container and Im having an interesting problem. I am unable to query the dns server from outside the container on my local machine, but it works fine from everywhere else... Unraid root@NAS:~# nslookup > apple.com Server: 192.168.1.7 Address: 192.168.1.7#53 Non-authoritative answer: Name: apple.com Address: 17.253.144.10 Name: apple.com Address: 2620:149:af0::10 > server 192.168.1.130 Default server: 192.168.1.130 Address: 192.168.1.130#53 > apple.com ;; communications error to 192.168.1.130#53: timed out ;; communications error to 192.168.1.130#53: timed out ;; communications error to 192.168.1.130#53: timed out ;; no servers could be reached Nitrogen (Another Linux box on my network) [ jameszy@nitrogen: ~ ] Sat Mar 11 11:11:19 $ nslookup > server 192.168.1.7 Default server: 192.168.1.7 Address: 192.168.1.7#53 > apple.com Server: 192.168.1.7 Address: 192.168.1.7#53 Non-authoritative answer: Name: apple.com Address: 17.253.144.10 Name: apple.com Address: 2620:149:af0::10 > server 192.168.1.130 Default server: 192.168.1.130 Address: 192.168.1.130#53 > apple.com Server: 192.168.1.130 Address: 192.168.1.130#53 Non-authoritative answer: Name: apple.com Address: 17.253.144.10 Name: apple.com Address: 2620:149:af0::10 So the problem is traffic cant traverse from unraid to the docker container, but traffic is not impeded from external sources to the docker container or to the bare metal unraid machine. I dont see any weird iptables rules, or odd route output... Docker containers are kind of confusing to me so im not sure where to start with troubleshooting.. Thanks!