0

CLI does not identify devices

Hi there,

I have nextdns setup in a raspberry pi with the following conf:

timeout 5s
discovery-dns 192.168.1.1
listen 192.168.1.1:53
log-queries false
cache-size 10MB
cache-max-age 0s
report-client-info true
setup-router true
config 9ace77
hardened-privacy false
bogus-priv true
max-inflight-requests 256
discovery-dns 192.168.1.1
detect-captive-portals false
auto-activate true
control /var/run/nextdns.sock
max-ttl 5s
mdns all
use-hosts true

 

Both bold lines have been an attempt to use this https://help.nextdns.io/t/35hzytw/nextdns-cli-not-reporting-hostname potencial fix however I still cannot get this to work.

Can you help me please? 

5 replies

null
    • jond_7
    • 2 yrs ago
    • Reported - view

    When you use setup-router=true, NextDNS CLI ignores any listen settings, see  

    nextdns config set -help

    You also have discovery-dns listed twice, but I don't think that is related to your issue. 

    The  discovery-dns should be the IP of the device handing out DHCP reservations, typically your router.  When you specify a "listen" IP, it refers to the host running NextDNS CLI. 

    What is the IP of your PI? What is the IP of your DHCP server?

    Update your config and restart your router and PI. See how that goes.

    • Pedro_Neves
    • 2 yrs ago
    • Reported - view

    Hi Jon, 

    Thanks for helping, I've done as you suggested and kept it like this: 


    hardened-privacy false
    bogus-priv true
    use-hosts true
    timeout 5s
    setup-router true
    log-queries false
    cache-max-age 0s
    cache-size 10MB
    max-inflight-requests 256
    auto-activate true
    listen 192.168.1.201:53
    control /var/run/nextdns.sock
    max-ttl 5s
    mdns all
    report-client-info true
    discovery-dns 192.168.1.1
    detect-captive-portals false
    config 9ace77
     

    My router IP is 192.168.1.1 and the pi is running on 192.168.1.201.  Does this look right? 

    I'm still getting device name # as you can see in the attached picture. What else can I try?

    cli conf
    • jond_7
    • 2 yrs ago
    • Reported - view

    First thing: when router-setup = true any configured listen is ignored; so set that to false, restart nextdns. (this probably doesn't matter though)

    Secondly, your graphic implies you have a LAN IP of 148.xx.xx.xx. 148.0.0.0/24 is a public IP space which should be behind a NAT router. So this is probably a cell phone on cell network? Then look to your nextDNS profile or the NextDNS app on the device. You should be able to configure the device name in the app.

      • Pedro_Neves
      • 2 yrs ago
      • Reported - view

      Jon Dagle Hey Jon, 

       

      Thanks for the help so far. So I've done as suggested and put router-setup = false 

      Maybe the example provided was not the best as it was only showing the public IP. Here is a new example. I've cleaned the logs so this is after the above change.

      It is my Homeassistant setup in the 192.168.1.234 but it still shows with no name and as you can see others are already poping up also with no identity... :( Any further advice?

      Untitled
      • jond_7
      • 7 mths ago
      • Reported - view

      In case you or anyone else is still struggling with missing device names (Device #ABDCE) or UUIDs (8b17ea4d-1bec-490b-a5b0-7f3f3cbef12a) in the logs, what fixed this for me was disabling mdns.

      nextdns config set -mdns=disabled

      mdns=all means that nextDNS CLI is "learning" device names from mdns/Bonjour on all interfaces. This picks up self-configured names like iPhone.local and even 8b17ea4d-1bec-490b-a5b0-7f3f3cbef12a.local. These seem to confuse the CLI and interfere with the authoritative name source for local devices (like a hosts file,  dnsmasq, or router handing out DHCP addresses).

      You can troubleshoot this by doing a reverse DNS lookup for devices using the IP of device missing name and IP of nextdns CLI (if CLI is on a different device, try both CLI and router): 

      dig +search +short -x 192.168.0.5 @192.168.0.1
MacMini01.

      You should get the local device name, as shown. If you get unexpected names or no name, then the CLI is probably not able to figure out the device name either.  The next step is to figure out why...

Login to reply

Content aside

  • 7 mths agoLast active
  • 5Replies
  • 1495Views
  • 2 Following