<![CDATA[Server in LAN is accessible globally but not locally]]>I have a hit a very weird problem in my career. After 1:1 NAT, The apache server installed in my LAN is accessible globally but not locally. I was configuring HAproxy, But hit the same roadblock. Please provide me a break through.

]]>https://forum.netgate.com/topic/115625/server-in-lan-is-accessible-globally-but-not-locallyRSS for NodeSat, 12 Sep 2026 04:47:14 GMTSat, 13 May 2017 12:21:27 GMT60<![CDATA[Reply to Server in LAN is accessible globally but not locally on Thu, 18 May 2017 14:02:46 GMT]]>It was pinging. The problem is solved. I had to set the DNS resolver to all the interfaces.

]]>https://forum.netgate.com/post/700455https://forum.netgate.com/post/700455Thu, 18 May 2017 14:02:46 GMT<![CDATA[Reply to Server in LAN is accessible globally but not locally on Wed, 17 May 2017 13:01:09 GMT]]>I assume you can ping it on the LAN but cannot access it using FQDN.

Is it a static or DHCP allocation. You can add the Hostname in the DHCP server with the IP address or you can add it as a Host Overide in DNS resolver. Either should work.

]]>https://forum.netgate.com/post/700180https://forum.netgate.com/post/700180Wed, 17 May 2017 13:01:09 GMT