Access internally hosted website from inside LAN using FQDN (NAT loopback?)

Installing and Using OpenWrt
1

Hi,

I'm trying to connect to my domain name "www.example.com" from inside the LAN but it fails. But it works fine if i'm not connected to the LAN.

For example:

  1. my external IP is 3.3.3.3
  2. my domain name www.example.com resolves to this 3.3.3.3 ip address.
  3. Inside the LAN the webserver is at 192.168.1.3 port 8080
  4. I have a port forward for anything coming in the WAN on port 80 -> 192.168.1.3:8080

When i access www.example.com from my cell phone with wifi turned off it works fine.

When i enable wifi on the cell phone and i'm connected to the LAN and i attempt to connect to www.example.com domain it times out.

What is the best way to resolve this?

It worked on the stock netgear firmware.

Thanks.

2

i guess you should try to use www.example.com:8080 or LAN-IP:8080 when accessing from the LAN side ?

3

that gives me a connection refused error.

4

Rebind the domain name to the server LAN IP:
https://openwrt.org/docs/guide-user/base-system/dhcp_configuration#hostnames
And make sure to specify its LAN port in the URL.

1 Like
5

Unfortunately i still get a connection refused. Here is what was added to /etc/config/dhcp

config domain
        option ip '192.168.1.3'
        option name 'www.example.com'

And from browser i tried to access: http://www.example.com:8080

1 Like
6

Verify that your LAN IP range is not filtered in the web server config.

7

It's not i can access it directly at http://192.168.1.3:8080 (although it brings me to the root website since it's missing the domain name header)

8

Each site in httpd typically has a separate config which can use a different set of allowed IPs.

9

did you restart dnsmasq afterwards ?

1 Like
10

I'm actually using nginx inside a docker container on a different server not httpd.

Yes i restarted dnsmasq, but I have dns setup to use google DNS.

I since the hostname is resolving to the external IP, I guess the real problem is how to use external IP address from inside the network.

11

set a rule on the outgoing traffic, to redirect to 192.168.1.3, or change the DNS.

1 Like
12

So in Luci, under interfaces->devices -> "br-lan" device, when i check the box for "promiscuous mode" then it works.

Is there any downsides to enabling promiscuous mode on the br-lan?