0

nextDNS CLI client names are wrong

I'm running nextDNS on my firewalla. It runs well, but I'd like to understand why some client names are very different than on the router. 

Note, this is CLI, not DoH. So I can't pass along a hostname that way. 

Of course I see IP address, but the names are mostly mangled or truncated. 

I have enabled  

-report-client-info

I see some discussions requesting that the client names be editable in logs. That would solve my probelm. If there is another way, I'd love to know. 

2 replies

null
    • R_P_M
    • 1 mth ago
    • Reported - view

    One way to add friendly device names to the CLI is to use the hosts file and add all your static local IPs of the devices + any name you want to associate with them. It doesn’t however work if the local IPs of the devices are changing.

    Oh, just to clarify the hosts file to edit/add is on the device running the CLI. 

      • Michael_Bierman
      • 1 mth ago
      • Reported - view

       Yeah, I don't see how that's workable. 

      1. I use as few IP reservations as possible. The router has local DNS so I can reach devices by hostname. 
      2. Firewalla has a UI for managing devices. Not easy to maintain parallel information.

      Somehow, CLI is forwarding partial hostnames, but I don't yet. understand the mechanism used to capture them. So maybe that could be enhanced?

      If privacy is an issue, maybe the real Mac address could be mapped to a unique value and sent to nextDNS logs once there was a unique identifier, users could create their own device names. 

Login to reply

Content aside

  • 1 mth agoLast active
  • 2Replies
  • 59Views
  • 2 Following