<![CDATA[Accessing domans from internal network]]>I am trying to get the ip nat loopback working so I can access the different domains from the inside of my network.

After searching the forum for some hours, and trying the different things, I am still getting the same behavior.

Tried to check and uncheck "Disable DNS Rebinding Checks" same for "Disable NAT Reflection for port forwards"

Didn't help, still either gave me the message about the attack, or the pfsense login page.

Tried the dns forwarding, but that didn't work either, instead nothing at all happen. (just the browser searching and searching)

What do I do now? When I was on version 1.2.3 it was doing what I wanted it to do.  :-[

]]>https://forum.netgate.com/topic/39685/accessing-domans-from-internal-networkRSS for NodeWed, 12 Aug 2026 06:30:31 GMTFri, 02 Dec 2011 21:31:37 GMT60<![CDATA[Reply to Accessing domans from internal network on Thu, 29 Dec 2011 16:07:25 GMT]]>Added the rules again with the switch I mentioned, and renamed my router (to router.mydomain.com).  This caused the dns lookup of server.mydomain.com to find the public IP of the machine, instead of the local IP of the router(192.168.1.1). From that point the NAT rules worked fine, redirecting my HTTPS port to the proper machine.

]]>https://forum.netgate.com/post/311031https://forum.netgate.com/post/311031Thu, 29 Dec 2011 16:07:25 GMT<![CDATA[Reply to Accessing domans from internal network on Thu, 29 Dec 2011 15:13:17 GMT]]>I also noticed, their is a "Nat Reflection" that can be turned on in the firewall rules.  Though it doesn't seem to help me either.

]]>https://forum.netgate.com/post/311016https://forum.netgate.com/post/311016Thu, 29 Dec 2011 15:13:17 GMT<![CDATA[Reply to Accessing domans from internal network on Thu, 29 Dec 2011 15:10:33 GMT]]>Same issue here.  Sounds like the feature is called NAT reflection, but I can't get it to work right.

]]>https://forum.netgate.com/post/311012https://forum.netgate.com/post/311012Thu, 29 Dec 2011 15:10:33 GMT