0

NextDNS daemon doesn't start on configured port

I just installed NextDNS on an EdgeRouter and changed the listen option to listen on a different port so it can coexist with DNSMasq:

david@RoutyMcRouterson# sudo nextdns config
use-hosts true
timeout 5s
max-inflight-requests 256
setup-router true
cache-size 0
cache-max-age 0s
bogus-priv true
listen 127.0.0.1:5555
control /var/run/nextdns.sock
discovery-dns
config eed2a1
max-ttl 0s
report-client-info true
auto-activate false
log-queries false
mdns all
detect-captive-portals false
hardened-privacy false

After restarting the service a couple times it appears the daemon is actually listening on port 5342:

Oct 11 18:01:39 RoutyMcRouterson nextdns[22942]: Received signal: terminated
Oct 11 18:01:39 RoutyMcRouterson nextdns[22942]: Stopping NextDNS 1.37.11/linux
Oct 11 18:01:39 RoutyMcRouterson nextdns[22942]: Restore router settings
Oct 11 18:01:40 RoutyMcRouterson nextdns[22942]: NextDNS 1.37.11/linux stopped
Oct 11 18:02:02 RoutyMcRouterson nextdns[23846]: Starting NextDNS 1.37.11/linux on 127.0.0.1:5342
Oct 11 18:02:02 RoutyMcRouterson nextdns[23846]: Listening on TCP/127.0.0.1:5342
Oct 11 18:02:02 RoutyMcRouterson nextdns[23846]: Starting mDNS discovery
Oct 11 18:02:02 RoutyMcRouterson nextdns[23846]: Listening on UDP/127.0.0.1:5342
Oct 11 18:02:07 RoutyMcRouterson nextdns[23846]: Setting up router
Oct 11 18:02:13 RoutyMcRouterson nextdns[23846]: Connected 45.90.28.0:443 (con=6ms tls=3248ms, TCP, TLS13)

 

Why is it not listening on 5555 as configured?

Reply

null

Content aside

  • 1 yr agoLast active
  • 138Views
  • 2 Following