-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Client names not resolving #43
Comments
Same here, with 2.61. Also running it in a VM with a separate physical Pi-hole. |
Im getting the same on 2.61 with PiAlert running on the same Pi as PiHole. PiHole resolves names |
At the moment Pi.Alert don't have device name resolution. BR |
Many thanks for the update. Looking forward to it! 🥳 |
Added Device name resolution using Reverse DNS in your LAN |
Pi.Alert 2.60 (2021-01-20).
Client names are not resolving, instead shows
(unknown)
for all clients except Router.No PiHole setup on the VM which runs Pi.Alert (PiHole on it's own Pi), this may be something to do with it as my previous installation was on same Pi as PiHole with
PIHOLE_ACTIVE = True
in/pialert/config/pialert.conf
and names resolved as expected. Can post more install info if needed.Clients names resolve on other devices/apps on network (Fing mobile app on iOS, Angry IP scanner on Windows, etc), Pi.Alert seems to be the only one which doesn't resolve.
The text was updated successfully, but these errors were encountered: