removing 127.0.0.1 from DNS search order
-
Here is what the current DNS server search order looks like.
Now, the LAN two based name-servers support the LAN based mail server as well as other loval servers. They are NOT the publicly available servers, though other than the local domain they get all the resolution from the net. So mail.netwright,net, resolves locally to 192.168.1.78 but publicly to via a public record it resolves to 58.69.150.45. My LAN based PC's have no problem resolving this as they are only resolving against the private nameservers, but cellphones when using local WiFi appear to run into problems with resolution, I am not sure, but it is possible that the reason might be that the Netgate appliance has the public address.
That is the reason I would like to remove 127.0.0.1 from the OS DNS resolution. Can I do this? The GUI doesn't seem to have a way. to accomplish this. If I SSH into the unit, can I change the value there?
-
@Ellis-Michael-Lieberman
The shown servers are used by pfSense only.
The point is, which servers your devices request to resolve host names.If pfSense is your DHCP server enter your local DNS servers in the DHCP settings of each enabled interface to hand them out to the clients.
If the mobile devices don't respect this for whatever reason, you can workaround this by port forwarding all DHCP requests to any other server than the local to one of your local servers.
However, my suspicion is, that the devices requests DoH servers in fact.
This could be prohibited by proper pfBlockerNG rules. -
@viragomann said in removing 127.0.0.1 from DNS search order:
If the mobile devices don't respect this for whatever reason, you can workaround this by port forwarding all DHCP requests to any other server than the local to one of your local servers.
…think you meant “DNS requests” here…
@Ellis-Michael-Lieberman if devices need to use pfSense for DNS you can use a host override or domain override. Remember IPv6 too, if enabled.
-
@SteveITS said in removing 127.0.0.1 from DNS search order:
…think you meant “DNS requests” here…
Yes, of course DNS.