Traffic Graph in 2.7.2 does not display description anymore? [resolved]
-
@xanaro said in Traffic Graph in 2.7.2 does not display description anymore, BUG?:
All of those hosts have a static IP and description set in the DHCP service
And did you maybe switch to kea - that does not currently support that?
-
Yup, I was just going to ask that. If you switched to Kea the hosts with existing leases would still be resolved but no new leases would be added.
Try switching back to ISC DHCPD if so.
-
I believe I did switch to kea for a few minutes because of the deprecation warning that I seen in the dashboard.
I then googled pfsense kea vs isc, and came to the conclusion that using kea was probably not a good idea for now and switched back to isc and checked the box to ignore deprecation warning. So kea was only on for a minute or two.
I have rebooted pfsense and all the machines since switching back to isc but the problem persists. (I had no idea that kea could have been the cause)
I may try another fresh 2.7.2 install and restore my XML config again, and make sure not to enable kea ever.
When you have 100 hosts on your network and your watching the traffic graph to see who is using the most, the IP addresses are less helpful than a hostname or description. With only the IP address visible I have to go lookup who that is in the DHCP server, it is inconvenient to say the least.
-
@xanaro does the IP resolve if you just query unbound for the PTR? If not then no it wouldn't be able to show you the names. But a reinstall seems like a sledge hammer approach to be honest.
-
One of the hosts that actually does show a description or hostname, does appear to have a PTR record. However most do not and resolve to nobody.invalid:
A good chunk of the hostnames are linux containers and VMs on proxmox, but there are also some workstations.
As you can see the first host resolves a PTR, the second does not, nearly all IPs are resolving to nobody.invalid.
-
I just figured it out! I noticed that the only two returning a PTR were the ones that I had some records set directly for in the unbound DNS resolver custom options box.
so I started looking that page over and noticed two unchecked boxes, once checked it all went back to working, thanks a ton @johnpoz
-
@xanaro registering dhcp can be problematic because every dhcp event will cause a restart of unbound... if you have your devices set with reservations - just load those, and not on every dhcp registration.
-
Thanks, I just unchecked the DHCP Registration, 95% of my hosts do have static entries.
-
If you have less than, say, 25 hosts it's not really an issue. Likely more than that.
-
@stephenw10 would depend on the lease time how many clients in sync with their renewals how long unbound taking to restart..
If your lease is long and only a few clients, unbound restarts how it should in like 2 seconds yeah prob never notice..
-
True. I guess I should specify, when using the default values or DHCP.
My test setup has more hosts than that and is served by a 3100. I never see any DNS issues.
