AdGuard Home (or other DSN-based ADBlocker)

  • Hi all!


    Just a quick question - I am looking to deploy a DNS AdBlocker like AdGuard Home or PiHole but I'm having some struggles as port 53 TCP and UDP are in use.

    As such the container fails to deploy and, I don't want to map 53 to another port, as otherwise the clients would not be able to connect.


    From netstat I can see that the port for both UDP and TCP is allocated to systemd-resolved.

    Code
    user@server:~# netstat -tulpn | grep ":53 "
    tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 794/systemd-resolve
    udp 0 0 127.0.0.53:53 0.0.0.0:* 794/systemd-resolve


    I'm not hosting any other DNS-serving container on Docker and, on OMV itself, I only have enabled SMB/CIFS, SSH and RSync Server.


    Could anyone help me in understanding why that port is in use and how I could free it so to map it to the container?


    Thank you!

  • Highly unlikely you really need to free that port. It is being listened to only on the loopback address, an address that other PCs on your LAN can never reach or need to reach.


    When you deploy any docker, just be sure it isn't configured to listen on that port and address combination on the host side.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 5.x on ASRock Rack C2550D4I C0 Stepping - 16GB ECC - Silverstone DS380 + Silverstone DS380 DAS Box.

  • Don't map to 0.0.0.0 unless there is some very specific reason that you must do that. Use the private LAN ip address.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 5.x on ASRock Rack C2550D4I C0 Stepping - 16GB ECC - Silverstone DS380 + Silverstone DS380 DAS Box.

  • kavejo

    Added the Label resolved

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!