You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ning currently only displays IP, MAC and manufacturer. It would be handy to also execute reverse DNS lookups for all discovered IPs. The local router usually has them registered with a more recognizeable device name.
Obviously this should only be done if the current DNS server being used has a local IPv4/IPv6 address.
i give this a +1, also make sure that it is working together with tools for dns based blocking (devices dns server(s) differ from dhcp provided/default gw) like DNS66. So allways use the matching local dns for the given interface (or even try all of them together with the ip of the default gw and dhcp server)
I came here from Fing, which got overloaded for my simple use-case of "Finding that one new IOT device in my home". Being able to recognize the existing devices by their rDNS names is essential for me, so I'll give Ning another look once this has been added.
Ning currently only displays IP, MAC and manufacturer. It would be handy to also execute reverse DNS lookups for all discovered IPs. The local router usually has them registered with a more recognizeable device name.
Obviously this should only be done if the current DNS server being used has a local IPv4/IPv6 address.
This might also partly solve #34
The text was updated successfully, but these errors were encountered: