Some DHCP clients have no DNS (unbound) records.
-
Been scouring Google and these forums for the past couple hours. Still no joy.
I think I have it set up correctly and, maybe that's why I'm having the trouble. Am I chasing a red herring? Local DNS is quirky. I have checked the box for DHCP Registration at Services > DNS Resolver > General Settings. And, when I check the table at Status > DHCP Leases, I see certain DHCP clients listed with their hostnames. It looks to be a mixed bag… I see some Windows clients, some Linux clients, some Kindles, an OpenELEC box, an HP printer and all the devices I set up to use a DHCP reservation. However, there are things I don't see... I don't see my XenServer or my Chromebook. Don't quote me on this but I think my Synology wasn't listed either until I gave it a DHCP reservation and had to provide the hostname.
I'm just curious if this is a strange quirk with pfsense or some issue with the clients. I guess I figured DHCP & DNS were all the same for any OS - meaning, DHCP hands out the IP (Obviously, this works just fine for all clients.) and said IP should just get logged as an a-record in DNS (Why does this part only work for some clients?). In any case, I'd like to think my settings are correct but I'd still like to know if anyone else has seen this issue. By all means, please correct me if I'm wrong and give me some ideas for fixes, should you have any.
-
Client responses can be the reason, check your DHCP logs for a failed client and one that worked and see if you can spot the differences. Been a long time since I looked but Dish Network boxes and Sonos gear were both giving my system fits. Blurry memory say one had no client name provided while the other reused the same client name on each system. Static assignments are what worked here so they may be your answer too.
