0

nextdns.sock not created by CLI 1.37.11 (freebsd)

I installed nextdns CLI v1.37.11 (freebsd) on PFSense+ 22.05 and it seems to be working well. nextdns.io says "All good! This device is using NextDNS with this configuration." Split-horizon DNS resolution for local hostnames works (unbound running on a high port), as does resolution for Internet hostnames. nextdns.io analytics is updating and I see the names of hosts on my local network in the analytics.

 

INFO: OS: pfsense

INFO: GOARCH: amd64

INFO: GOOS: freebsd

INFO: NEXTDNS_BIN: /usr/local/sbin/nextdns

INFO: INSTALL_RELEASE: 1.37.11

 

The CLI seems to be operating correctly, except that /var/run/nextdns.sock never gets created. 

Consequently I can't run nextdns (cache-stats | cache-keys | trace | discovered).  When I do, I get "Error: dial unix /var/run/nextdns.sock: connect: no such file or directory".  /var/run/nextdns.pid does get created.

Q1: Is this to be expected?  And if not, what can I do to ensure that nextdns.sock gets created?

Q2: When I 'nextdns restart' or 'nextdns start' and look in the logs, I see 'NextDNS 1.37.11/freebsd stopped'.  Is that to be expected?

nextdns[98379]: Starting NextDNS 1.37.11/freebsd on localhost:53, <LAN IPv4>:53

nextdns[98379]: Starting mDNS discovery

nextdns[98379]: Listening on UDP/127.0.0.1:53

nextdns[98379]: Listening on TCP/[::1]:53

nextdns[98379]: Listening on UDP/[::1]:53

nextdns[98379]: Listening on TCP/127.0.0.1:53

nextdns[98379]: Listening on UDP/<LAN IPv4>:53

nextdns[98379]: Listening on TCP/<LAN IPv4>:53

nextdns[2156]: NextDNS 1.37.11/freebsd stopped

nextdns[98379]: Connected <nextdns IPv4>:443 (con=7ms tls=88ms, TCP, TLS13)

nextdns[98379]: Connected <nextdns IPv4>:443 (con=5ms tls=70ms, TCP, TLS13)

nextdns[98379]: Switching endpoint: https://dns.nextdns.io#<nextdns IPv4>,<nextdns IPv6>

nextdns[98379]: Activating

4 replies

null
    • Rob_Cork
    • 2 yrs ago
    • Reported - view

    I see the same issue as well on pfsense 22.05.

    • Rob_Cork
    • 2 yrs ago
    • Reported - view

    I found a way to work around this bug. I changed my config to have the file created in /tmp 

    control /tmp/nextdns.sock

    After restarting nextdns i can see the nextdns.sock file is created correctly in /tmp directory. However, running nextdns cache-stats still results in the same error about the file missing from /var/run/nextdns.sock so it appears that this path is hardcoded in the cli. 

    So  i created a softlink to /var/run/netxtnds.sock by running the following command from pfsense shell 

    cd /var/run
ln -s /tmp/nextdns.sock nextdns.sock

    Now when running nextdns cache-status it works correctly. I'm not sure if this will survive a reboot but will try and report back.

      • Rob_Cork
      • 2 yrs ago
      • Reported - view

      This fix does not survive a reboot so i installed the shellcmd pfsense package and added an entry for 

      ln -s /tmp/nextdns.sock /var/run/nextdns.sock

      Now after pfsense reboots its working as expected

    • Michael_K.1
    • 2 yrs ago
    • Reported - view

    Thanks for those suggestions, Rob.

     

    For anyone else following this, it's also being discussed in this thread:

    https://help.nextdns.io/t/y4hgc1c/varrunnextdns-sock-connect-no-such-file-or-directory

Login to reply

Content aside

  • 2 yrs agoLast active
  • 4Replies
  • 152Views
  • 2 Following