No internet connection after pointing router to AdGuardHome

[harrismck]

Prerequisites

• I have checked the Wiki and Discussions and found no answer

• I have searched other issues and found no duplicates

• I have set up AdGuard Home correctly and configured clients to use it

Platform (OS and CPU architecture)

Ubuntu Server 22.04.3, x86_64

Installation

Docker compose

Issue

After installing AdguardHome via docker compose, and pointing my router to use it as the DNS server, I have no DNS access at all. I can still ping ips between my machines, but that's it. The query logs in the AdguardHome admin panel are also completely blank. I tried setting this up the other day and at least there was queries in the logs (but still a broken connection).

The relevant snippet of my docker compose:

  adguardhome:
    container_name: adguardhome
    image: adguard/adguardhome
    volumes:
      - ./config/adguardhome/work:/opt/adguardhome/work
      - ./config/adguardhome/conf:/opt/adguardhome/conf
    ports:
      - "53:53/tcp" # DNS
      - "192.168.1.111:53:53/udp" # DNS (needs the full IP or docker containers can't reach each other??)
      - "67:67/udp" # DHCP
      - "68:68/udp" # DHCP
      - "68:68/tcp" # DHCP
      #- "80:80/tcp" # These are for using adguardhome as an HTTPS/DNS-over-HTTPS, but NPM uses these ports too...
      #- "443:443/tcp"
      #- "443:443/udp"
      - "3434:3000/tcp" # Initial config port: 3434 (default is 3000 but homepage is using that)
      - "853:853/tcp"
      - "784:784/udp"
      - "853:853/udp"
      - "8853:8853/udp"
      - "5443:5443/tcp"
      - "5443:5443/udp"
      - "9999:9999" # Web UI port set in initial config
    restart: unless-stopped

Router settings:

AdGuardHome panel:

[DeltaTango69]

I am strugglin also with this information 127.0.0.1 vcan never work because this IP is not in the range from your router. You have to enter the IP where Adguard is installed, also for example 192.168.1.105

[he-pennypacker]

Your router setup won't work as you are telling it to use the localhost (127.0.0.1) of the router.

Set the primary DNS to the IP address where your docker is running (is it 192.168.1.111 ?) and delete the entry you have for secondary DNS.

I also don't like this entry in your compose.yaml, it seems unnecessary.

192.168.1.111:53:53/udp

Finally, you have exposed every port from container to host, most are only needed for running specific services (e.g. DNSCrypt, DNS over QUIC etc). I would blow away your current compose.yaml and try something like this (this assumes you are only using DNS and web admin, and not using DHCP server, DNS Crypt, DNS over QUIC, or debugging profiles).

Note that in this configuration, you won't see the client IP addresses in the log as the github wiki tells you - https://github.com/AdguardTeam/AdGuardHome/wiki/Docker

services:
adguardhome:
container_name: adguardhome
restart: unless-stopped
volumes:
- /my/own/workdir:/opt/adguardhome/work
- /my/own/confdir:/opt/adguardhome/conf
ports:
- 53:53/tcp
- 53:53/udp
- 80:80/tcp
- 443:443/tcp
- 443:443/udp
- 3000:3000/tcp
image: adguard/adguardhome

Alternatively, if you want to simplify your life, you can run your adguardhome container network in host mode, like this. You will then see client IPs in the log, instead of the container IP. The drawback is that you can't adjust ports so you might have some conflicts between containers.

Let us know how you go.

services:
adguardhome:
container_name: adguardhome
restart: unless-stopped
volumes:
- /my/own/workdir:/opt/adguardhome/work
- /my/own/confdir:/opt/adguardhome/conf
network_mode: host
image: adguard/adguardhome

[harrismck]

Hi! It's been a while. I finally had some time to give this a go again, and yup, that was it. Can't believe it was as simple as putting the actual local IP of my server in there... Kinda wild that all the docs just seem to insist on entering the loopback address.

My router doesn't allow only one DNS address, but it does allow putting the same one in twice, so that worked!

I do actually see client IP addresses in the logs, even with my container not in host mode.

Anyway, thanks a lot for your help!