Not sure what to call this problem. Failure to resolve namespace on lan but not wan?
-
Not sure what this problem would be called or even what it relates to. I'm new to pfsense and I've never experienced this problem on any other router.
I've got a server running inside my lan network, lets call it 192.168.1.100
I can access it just fine by typing in that address from any device within the lan network.
I've got that address port forwarded on the router such that I can access it when outside of the network. Lets call it http://server.net
All of the above works just fine. But when I try to access http://server.net while inside my local lan network, I get a failure to resolve. For example, on my phone I can access it just fine while inside the lan by manually going to 192.168.1.100, but my apps don't use that local address, they try to connect through the server's wan namespace (http://server.net), and it fails every time.
I never had this problem on my old asus router running merlin firmware, so I'm a bit lost as to where to even being addressing this problem.
Any assistance or suggestions would be helpful. Thanks!
-
@christophermay
Are you using an internal DNS?
By default pfSense provide DNS resolution. So you can add an override for your public host name.Otherwise you have to enalbe NAT reflection in the NAT rule or globally in the advanced settings.
-
Thanks a lot, that did the trick! I've never had to use a DNS resolver override before on any other router.
-
@christophermay
These other routers (presumably consumer routers) might have had NAT reflection enabled by default (without the ability to disable it), but that has other drawbacks.
DNS override is the more reliable solution for that in the end.