标签： systemd-resolved

https://adguard-dns.io/kb/zh-CN/adguard-home/faq/#bindinuse This happens because the port 53 on localhost, which is used for DNS, is already taken by another program. Ubuntu comes with a local DNS called systemd-resolved, which uses the address 127.0.0.53:53, thus preventing AdGuard Home from binding to 127.0.0.1:53. You can see this by running: sudo lsof -i :53 The output should be similar to: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAMEsystemd-r 14542 systemd-resolve 13u IPv4 86178 0t0 UDP 127.0.0.53:domainsystemd-r 14542 systemd-resolve 14u IPv4 86179 0t0 TCP 127.0.0.53:domain To fix this, you must either disable the systemd-resolved daemon or choose a different network interface and bind your AdGuard Home to an accessible IP address on it, such as the IP address of your router inside your network. But if you do need to listen on localhost, there are several solutions. Firstly, AdGuard Home can detect such configurations and disable systemd-resolved for you if you press the Fix button located next to the address already in use message on the installation screen. Secondly, if that doesn’t work, follow the instructions below. Note that if you’re using AdGuard...