Logs - Rename Devices
It would be tremendously helpful to be able to identify devices in the logs tab that come from NextDNS CLI that are not correctly identified. Would it be possible to rename devices (e.g. from "Device #3HRCE" to "Google Home Mini") to help identify relevant logs? Seems they are randomly named and do not line up with mac address.
-
+1! Would be great if there was an option to add a device name linked to a MAC address. Comparable to the way you can link a configuration to a specific MAC address.
-
Willem I think you mean IP. MAC address never leave the network boundary.
-
Martheen not entirely. In my setup, I've only set nextDNS on my UDM Pro. Not on the seperate devices. If I'm not at home I can open a VPN connection in order to route through NextDNS.
I'm using the Conditional Configuration to link configuration files to devices using:
sudo nextdns config set -config 10.0.4.0/24=12345 -config 00:1c:42:2e:60:4a=67890 -config abcdef sudo nextdns restartthis same notation could be used to setup a device name
-
Some DNS clients/stub resolvers (like DNSMasq) can also send the client's MAC with DNS requests.
-
-
would be super helpful
-
+1
-
+1
-
+1
-
+1
-
+1
-
Yes this would be great! +1. Also maybe a way to merge devices? For example if a single physical device comes up in the logs as two devices(which can occur for several reasons) - an ability to merge those two devices into a single device, with the logs all merging.
-
Good afternoon Romain Cointepas & Olivier Poitrey ,
Thanks for everything you do. Hoping to get some traction on some of these postings. I used to post on Reddit and never got a response, but then started here once this site went live. Any info on these requests?
Thanks so much!
-
+1 Its nice seeing the different devices but i have no way to understand which device is which without thoroughly researching. Even the ability to set aliases in the portal would be helpful.
-
Setting/overwriting device names in web UI would be great.
-
I agree with this as well. Just having a manual tab to be able to name a device like my vaccum because you know that's where the request is coming from.
-
With DoT and DoH you can add device name at used DoH / DoT "URL" which solve your idea.
No need for adding unnecessary features.
-
DynamicNotSlow Not every device supports DoH or DoT (e.g. my wireless outlets don't support DoH or DoT). This is why I use NextDNS CLI for DoH.
Still a need to have the ability to rename devices according to all the other people that upvoted and replied.
-
-
It would be great to have the option to set an alias for devices within the Portal so they have a friendly name in the logs. Maybe with the UDM/UDMP install it could include something like the discovery-dns option (maybe something like discovery-alias) to get the alias assigned within UnifiOS and pass that info to the alias field in the Portal?
-
Kevin This was exactly how I was hoping it would work. I have all of my devices set up with Static IPs and aliases, so it sucks to not have that work picked up by NextDNS.
-
-
Agreed, this would be very helpful for those applying these changes at the router level.
-
Why can't nextdns know this information without having to have a app installed. They link your outside address to your login...
-
Tommy Moree what? you don't need install anything for using NextDNS.
-
-
+1 the names really aren't that friendly at the moment. I would love to be able to add a custom name to a device
-
Rename would be awesome, and an option to hide devices would also help.
-
As other mentioned, renaming / aliasing devices would be pretty nice. Also, for those that install the app, you could send a fixed UUID, regardless of the name of the device, which can have a collision.
Then, we could be able to rename or alias the provided name into whatever the admin wants to see in the logs / analytics page.
-
Support having the facility to rename devices or name not identified ones.
-
Yes this is really missing, adguardhome has this as well in the config where you can add tags and names per device.
