Replies: 1 comment 1 reply
-
|
@N3RO365 thanks for the detailed report. The scanners responsible for name resolution are Also, check this documentation: https://jokob-sk.github.io/NetAlertX/REVERSE_DNS/?h=name#setting-up-better-name-discovery-with-reverse-dns If you know how to code you could probably even create a Fritzbox plugin. There seems to be an API for it (maybe this), but I don't own any of these devices so I can't test or implement this. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your answer. How can i Specifying the DNS in the container by using docker on unraid? I think that's the only other thing I could try. |
Beta Was this translation helpful? Give feedback.
-
Hi.
I use NetAlertX and Adguard Home on Unraid in Docker with its own IP.
I use a Fritzbox as my router. The IP is 192.168.178.1. I have set this IP in Private inverse DNS-Server in Adguard Home.
I have added this in the NetAlertX settings:
Only the dockers are recognized correctly during a scan. Everything else is not recognized at all or incorrectly (Android-2?).
When I use Nslookup on a device, I always get this error message:
All devices have been given a name in the Fritzbox, but somehow the names are not recognized by NetAlertX.
What could be the reason for this? Is it Adguard Home or have I not set something correctly?
Or is there no option and I have to change the names of the devices concerned manually?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions