0

NextDNS fails to work on UXG-Lite

Used the install script, and it seemed to setup correctly. Tried starting nextdns, and checking the status

root@UXG-Lite:~# nextdns status
Error: service in failed state

Checked the logs:

Dec 23 20:53:28 UXG-Lite systemd[1]: Started NextDNS DNS53 to DoH proxy..
Dec 23 20:53:29 UXG-Lite nextdns[2545]: Starting NextDNS 1.41.0/linux on :53
Dec 23 20:53:29 UXG-Lite nextdns[2545]: Listening on TCP/:53
Dec 23 20:53:29 UXG-Lite nextdns[2545]: Starting mDNS discovery
Dec 23 20:53:29 UXG-Lite nextdns[2545]: Listening on UDP/:53
Dec 23 20:53:29 UXG-Lite nextdns[2545]: Startup failed: proxy: tcp: listen tcp :53: bind: address already in use
Dec 23 20:53:29 UXG-Lite nextdns[2545]: Error: proxy: tcp: listen tcp :53: bind: address already in use
Dec 23 20:53:29 UXG-Lite systemd[1]: nextdns.service: Main process exited, code=exited, status=1/FAILURE
Dec 23 20:53:29 UXG-Lite systemd[1]: nextdns.service: Failed with result 'exit-code'.

Unsure if relevant info, but the UXG-Lite runs Debian, and it seems systemd-resolved service does not run by default.

3 replies

null
    • R_P_M
    • 11 mths ago
    • Reported - view

    It’s saying that there’s something else running on port 53 already.

    Can you run netstat or equivalent to find out what’s listening on the port?

      • Evie
      • 11 mths ago
      • Reported - view

      I couldn't find anything with netstat. but lsof came up with... systemd and dnsmasq?

      root@UXG-Lite:~# lsof -i:53
COMMAND  PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
systemd    1   root   27u  IPv4   8188      0t0  TCP 127.0.2.1:domain (LISTEN)
systemd    1   root   29u  IPv4   8189      0t0  UDP 127.0.2.1:domain
dnsmasq 2811 nobody    6u  IPv4  18542      0t0  UDP 192.168.12.1:domain
dnsmasq 2811 nobody    7u  IPv4  18543      0t0  TCP 192.168.12.1:domain (LISTEN)
dnsmasq 2811 nobody    8u  IPv4  18544      0t0  UDP 10.10.10.1:domain
dnsmasq 2811 nobody    9u  IPv4  18545      0t0  TCP 10.10.10.1:domain (LISTEN)
dnsmasq 2811 nobody   10u  IPv4  18546      0t0  UDP setup.ui.com:domain
dnsmasq 2811 nobody   11u  IPv4  18547      0t0  TCP setup.ui.com:domain (LISTEN)
dnsmasq 2811 nobody   12u  IPv4  18548      0t0  UDP localhost:domain
dnsmasq 2811 nobody   13u  IPv4  18549      0t0  TCP localhost:domain (LISTEN)
dnsmasq 2811 nobody   14u  IPv6  18550      0t0  UDP [fe80::f6e2:c6ff:fee8:beaf]:domain
dnsmasq 2811 nobody   15u  IPv6  18551      0t0  TCP [fe80::f6e2:c6ff:fee8:beaf]:domain (LISTEN)
dnsmasq 2811 nobody   16u  IPv6  18552      0t0  UDP [fe80::f6e2:c6ff:fee8:beaf]:domain
dnsmasq 2811 nobody   17u  IPv6  18553      0t0  TCP [fe80::f6e2:c6ff:fee8:beaf]:domain (LISTEN)
dnsmasq 2811 nobody   18u  IPv6  18554      0t0  UDP [fe80::f6e2:c6ff:fee8:beaf]:domain
dnsmasq 2811 nobody   19u  IPv6  18555      0t0  TCP [fe80::f6e2:c6ff:fee8:beaf]:domain (LISTEN)
dnsmasq 2811 nobody   20u  IPv6  18556      0t0  UDP localhost:domain
dnsmasq 2811 nobody   21u  IPv6  18557      0t0  TCP localhost:domain (LISTEN)
dnsmasq 2811 nobody   26u  IPv4  20107      0t0  UDP 203.0.113.1:domain
dnsmasq 2811 nobody   28u  IPv4  20108      0t0  TCP 203.0.113.1:domain (LISTEN)
dnsmasq 2811 nobody   29u  IPv6  20466      0t0  UDP [fe80::c4a8:5eff:fe39:d982]:domain
dnsmasq 2811 nobody   30u  IPv6  20467      0t0  TCP [fe80::c4a8:5eff:fe39:d982]:domain (LISTEN)
dnsmasq 2811 nobody   31u  IPv6  21542      0t0  UDP [2001:db8:1000::1]:domain
dnsmasq 2811 nobody   32u  IPv6  21543      0t0  TCP [2001:db8:1000::1]:domain (LISTEN)

      But checking the dnsmasq service, it seems inactive.

      root@UXG-Lite:~# systemctl status dnsmasq
● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
     Loaded: loaded (/lib/systemd/system/dnsmasq.service; disabled; vendor preset: enabled)
     Active: inactive (dead)

      On another note, I did somehow get nextdns running, after uninstalling and reinstalling with `apt-get` instead of the `install.sh` script. I actually can't remember if it was successful on my very first install.

      But in any case, restarting nextdns seems to bring it back to the failed state, even if it was running fine just before.

    • Evie
    • 11 mths ago
    • Reported - view

    I edited  /etc/systemd/resolved.conf to have DNSStubListener=no

    Then rebooted, and was able to successfully run `nextdns start`. And it seems now it's able to survive restarting.

Login to reply

Content aside

  • 11 mths agoLast active
  • 3Replies
  • 208Views
  • 2 Following