PFSense Newbie Question: DHCP and DNS Domain
-
Dear PFSense community,
I've recently switched from dd-wrt to PFSense and I couldn't be happier. There is just one thing that seems fishy to me and that had worked flawlessly on my old R7000 Netgear router with dd-wrt.
I'm running PFSense with both DNS Resolver and DHCP Server enabled, including offering DHCP leases to the DNS server. My LAN domain 'pikespeak' is configured in the general setup. This is the same setup as I had on dd-wrt; though, after switching to PFSense my homeassitant instance is not able to reach other clients in the net (they were not configured with the FQDN like 'client1.pikespeak' but just as a host name, i.e. 'client1'). Also, my other clients on the LAN cannot reach at least some of the other clients and servers without stipulating the domain suffix. It is very obvious on my Windows 10 PC:
Ethernet adapter Ethernet 6:
Connection-specific DNS Suffix . : pikespeak
IPv4 Address. . . . . . . . . . . : 192.168.2.123
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.200Apparently the DNS suffix is pulled correctly but I can only resolve some of the hosts and I need to add the domain suffix for others. The same behavior is observed on my wife's Chromebook and on my Linux machine as well.
I've tried adding a search domain but the issue prevails.
I appreciate any suggestion or comment. Thank you!