@The-Party-of-Hell-No
THANKS for the questions! My apologies for delays... lots of life here...
When I say "Unbound really doesn't like local devices registering themselves" I'm referring to the fact that:
The Unbound design only adds a device to its database when loading the database
Thus, if device self-registration is enabled, Unbound must reload
On a busy system (eg we have a mailserver that must filter a LOT of email attempts), any Unbound reload is a significant hit.
Your final question: connections are via BOTH wireless AP and wired. All DHCP is handled by pfSense, so it really doesn't matter if wired or wifi. (Which IP is used depends on the subnet being accessed, which is determined by either wired port or wireless SSID.)
I'm not concerned about how to accomplish the combination of internal+external. As you note, it's pretty simple. This network has been running for some time.
My questions are specific to the two situations listed:
What's a good solution for local device registration
and
What's a good solution for handling roving internal device DNS. YES -- known devices with static IP's assigned on each subnet.
Just to make it clear, an example:
Laptop AdminA has preassigned static IP's:
192.168.11.10
192.168.220.10
10.8.0.10
172.16.99.10
...on each of four subnets (public, server, secure internal, etc)
Unfortunately, while pfSense DHCP properly assigns the correct IP address every time, on the DNS side, any internal DNS query is handed whichever IP is listed first in /etc/hosts for AdminA. :(
That's the problem I'm asking about in #2.