0

« Device xxxxx » on my configuration

Hi everyone, I have this kind of trouble with my configuration : I have a raspberry Pi running NextDNS cli with discovered configured and plain text hostnames on /etc/hosts. My router serve also as DHCP with all my devices static IP, so I have setup the /etc/hosts, and addressing the DNS to my RasPi. Only this DNS, no other ones.  I also configured the DHCPv6 and DNSv6 as they are set on my NextDNS config. All my Apple’s device are configured with a profile, except the HomePod mini. Any clue ? Is there some IPv6 leaking from some devices ?

14 replies

null
    • R_P_M
    • 1 yr ago
    • Reported - view

    Just how old are the logs for those mystery devices? Maybe they are old ones from before you finished setting up everything?

      • puchijon
      • 1 yr ago
      • Reported - view

      R P M They was from a 2 weeks ago, I often flush the logs, maybe every weeks. And it is still coming again.

      • puchijon
      • 1 yr ago
      • Reported - view

      R P M Some screenshots :   

    • puchijon
    • 1 yr ago
    • Reported - view

    Hi, I'm still experiencing like 50 "Device #XXXXX", even if I flush the logs they still appear. I still have my NextDNS CLI configured and it shows my own devices but show also the unidentified. I don't know why...

      • R_P_M
      • 1 yr ago
      • Reported - view

      Johnny BOI Hello again. Quick question, what listen settings are set in the nextdns.conf? If more than one, which order do they appear in?

      • puchijon
      • 1 yr ago
      • Reported - view

      R P M Hi, thank you for your answer, here is the config of my NextDNS CLI :

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

      and the "hosts" file looks like this :

      • puchijon
      • 1 yr ago
      • Reported - view

      Johnny BOI PS : I have flush logs yesterday and so far I only have one unidentified device with this as a request : ip.parrotdns.com

      • R_P_M
      • 1 yr ago
      • Reported - view

      Johnny BOI Are these “unidentified devices” using an IPv6 address in the logs?

      By using the DNS IPv6 addresses in DHCPv6 you would expect to see them appear as unidentified in the logs (with only an IPv6 address to identify them). With the CLI running you don’t need to have the DNSv6 set. Please try removing them from the DHCPv6 setup. 

      • puchijon
      • 1 yr ago
      • Reported - view

      R P M Okay, thanks, I just disabled DHCPv6 on my router, but my ISP doesn't allow the deactivation of IPv6, is this a problem ? As well, for DNSv6 I putted the ones that's written on my NextDNS config, should I disable everything ? Except the IPv6 ?

      EDIT : typo

      • R_P_M
      • 1 yr ago
      • Reported - view

      Johnny BOI You just need to remove the DNSv6 IPs from DHCPv6, not disable it completely. 

      Does the DHCPv6 setup allow an empty DNS setting?

      • puchijon
      • 1 yr ago
      • Reported - view

      R P M Yes, my ISP uses its own DNSv6 servers so I can deactivate DHCPv6 and remove the entries of NextDNS from DNSv6 but the IPv6 will still be activated as there is no way to disable it.

      • R_P_M
      • 1 yr ago
      • Reported - view

      Johnny BOI Disabling DHCPv6 should be ok for the time being. 

      Ideally if you could find out the router’s link local IPv6 address, that would be the better option to put into the DNSv6 settings and then you can use DHCPv6 again. 

      • puchijon
      • 1 yr ago
      • Reported - view

      R P M yes I see, I will try that, thanks a lot for your help, advices !

    • brianp9906
    • 7 mths ago
    • Reported - view

    Thanks for this posting.  I tracked down my issue with Opnsense firewall.

    I have both IPv4 and IPv6 traffic, but hard set the DHCP DNS server to my IPv4 internal DNS for dnsmasq+nextdns CLI to ensure that NextDNS CLI can properly label (hostname) DNS lookup traffic.  Before doing this, any IPv6 traffic from hosts was just labeled from a unique Device ID number, not the DHCP hostname from IPv4 registration.  Now my IPv6 traffic uses DNS IPv4 for both lookups and they work properly.

Content aside

  • 7 mths agoLast active
  • 14Replies
  • 307Views
  • 3 Following