Issue with LANCache DNS in different server than monolithic
reddit / selfhosted

----------------------------------------------------------------------
claubervs · 2023-12-16 22:21

Hello,

I am facing a issue with setting up my Lancache DNS at a different
server than my monolithic instance. Let me describe my setup below:

**Current:** I have my UNRAID server running both Lancache Monolithic
and DNS without any problems.

**Changes**:  I would like to move my DNS to another server that has a
better uptime while keeping the monolithic service in UNRAID.

The reason is that my UNRAID has the storage space for the cached
files and the other server holds all my internet DNS routing. Whenever
I have to take my UNRAID down for maintenance or some other reason I
end up loosing DNS routing.

The other server is an always online Zima board, used as my router
with OPNSense and Adguard Home. My DNS traffic currently goes:

* OPNSense (Zima) -> Adguard (Zima) -> LANCache DNS (**UNRAID**) ->
Cloudflare DNS.

This change would make it:

* OPNSense (Zima) -> Adguard (Zima) -> LANCache DNS (**Zima**) ->
Cloudflare DNS

 I believe my problem lies in the docker compose file that I am using
for LANCache DNS. Although the container runs and says it is up, when
I put the IP address in Adguard, I loose my DNS routing.

* 10.10.10.43 is the Static IP I am assigning in this compose file for
the LANCache DNS.
* 10.10.10.45 is my monolithic instance in UNRAID

​

    version: "3.3"
    services:
      lancache-dns:
        container_name: lancache-dns
        ports:
          - 10.10.10.43:53:53/udp
          - 10.10.10.43:53:53/tcp
        environment:
          - DNS-Port=53
          - USE_GENERIC_CACHE=true
          - LANCACHE_IP=10.10.10.45
          - UPSTREAM_DNS=1.1.1.1
          - DISABLE_WARFRAME=true
          - DISABLE_RIOT=true
          - DISABLE_RENEGADEX=true
          - DISABLE_DAYBREAK=true
          - DISABLE_CITYOFHEROES=true
        image: lancachenet/lancache-dns:latest
        hostname: lancache-dns
        restart: unless-stopped
        network_mode: host

Would anyone be able to shed some light in this for me? I can include
more information if needed.

Thanks

----------------------------------------------------------------------
thekrautboy · 2023-12-16 22:44

> 10.10.10.43 is the Static IP I am assigning in this compose file for
the LANCache DNS

How are you assigning that IP? Is that the IP of the Docker host
machine that runs the DNS container?

----------------------------------------------------------------------
claubervs · 2023-12-16 23:10

>How are you assigning that IP? Is that the IP of the Docker host
machine that runs the DNS container?

This might be the issue, the only place I believe I am assigning the
IP is in this compose that I posted.

>And your Adguard is running on the same machine as this lancache DNS?
Are both running as Docker containers? Share the Adguard compose then.

AdGuard is running on the same VM as OPNSense (as a service inside
OPNSense) and shares the same IP. OPNSense runs directly in the VM, no
docker. AdGuard is a service from OPNSense, no docker.

Another VM runs ubuntu server with docker which I am using to setup
lancache dns. I am trying to use the host network so that way I can
assign an IP that is on the same net as all my services.

​

I might be completely wrong on the way I am assigning the static IP to
my compose there.

----------------------------------------------------------------------
thekrautboy · 2023-12-16 23:13

> This might be the issue, the only place I believe I am assigning the
IP is in this compose that I posted.

You mean these lines?

> ports:
 - 10.10.10.43:53:53/udp
 - 10.10.10.43:53:53/tcp

That is not assigning the IP at all. You are simply telling the
container "hey if you can, map these port so that IP". But if that IP
doesnt exist on the host, it cannot map it.

----------------------------------------------------------------------
claubervs · 2023-12-17 00:05

Thanks, that solved the issue. I was not entirely sure it was my
docker configuration, although I suspected it.

Anyway, thanks again!

----------------------------------------------------------------------
thekrautboy · 2023-12-17 00:32

You didnt "assign" the IP to that container as you thought you were.