LIke you asked here. No.
https://subdomain.mydomain.com → 192.168.10.150:8123
https://subdomain2.anotherdomain.com → 192.168.10.160:9870
You would need to change the webserver config to direct requests from the local LAN subnet on http(s) to the right content.
I have just checked NAT Hairpinning (which is what you asked for) on my Balance One here and it worked fine.
So I have a port mapping in place on the WAN:
WAN-IP:6666 → LAN-IP:5000
And I can access that from within my network fine (so my LAN-IP → WAN-IP:6666->LAN-IP:5000.
I think you need some Peplink Engineering help to diagnose this issue you are seeing there.
1 Like
Thank you Martin, you’ve been extremely helpful
That’s exactly what i’m after. I will contact support now.
Is this set in Network → NAT Mappings?
1 Like
No in Network > Inbound Access | Port Forwarding That is how you set up WAN to LAN port forwarding as usual and NAT hairpinning typically ‘just works’.
I’ve got a little further with support ticket. It seems that linux ping recognises the DNS and my phone, but neither windows 10 machine is happy.
My only concern with using the port forward, is that it seems to open that port to WWW. Which i dont want to do. I tried adding an inbound firewall rule, but that didn’t seem to block the port to the web.
For posterity it was a Secure DNS “protection” in AVG i never knew i had.
Thanks for your help
1 Like