Pinging local computer name resolves to WAN IP.
-
I've had an issue where Win10 computers that are assigned an IP via DHCP have been unable to access other computers through their //ComputerName when using explorer. All the computers can be pinged and accessed through their IP addresses, so while not a critical issue, it is a bit annoying. After a little digging I found that pinging any ComputerName from a DHCP'd computer is resolving to the WAN IP which I assume is being caused by some setting in the DNS Resolver. Any device that has Static DHCP Mappings assigned in pfSense can be pinged and accessed through their set Hostname without issue, but I would rather not have to static map every computer either in pfSense or in that computers network settings. So the question is, what setting am I looking for that will keep local name requests local?
Other notes:
IPV4 only
Pure NAT for reflection and port forwarding.
I am using my purchased domain name in general setup.
From what I can tell "Register DHCP leases in the DNS Resolver" is no longer a selectable option as it never worked. -
@r2the3rd said in Pinging local computer name resolves to WAN IP.:
I am using my purchased domain name in general setup.
That is going to be problematic out of the gate with caveats that have to be taken into account.. Registering dhcp clients has always been problematic since it requires a restart of unbound on every dhcp event.
if you want host.domain.tld to resolve to a local IP, create a local entry is the most sure fire way to make sure the fqdn resolves to the IP you want.
If you switched over to the kea then registration isn't a thing yet..
