that's the funny part it works from outside the LAN, but not from another compouter within the LAN
You may need to play DNS tricks to get the local systems to see the local IP [to connect to it that way].
Otherwise, the router needs to support "hairpinning".
See: Network address translation - Wikipedia
hi, what exactly do you need to do, what to check, what to try, maybe I did something wrong.
When you are connecting from an outside network:
a.b.c.d > 50.99.215.64 the router forwards to 192.168.1.76
Things will work as expected.
When you are connecting from the same network:
192.168.1.x > 192.168.1.76
Things will work as expected [no routing required].
When you use global DNS to resolve the name, it returns an IP outside of the local network.
So...
When you are connecting from the same network:
192.168.1.x > 50.99.215.64 and the router doesn't know how to handle that connection.
Things will not work as expected [hairpin routing required].
With Hairpinning it looks like this:
192.168.1.x > 50.99.215.64 [client to router]
[the router changes the destination and the source - like a proxy would]
router.LAN.IP > 192.168.1.76 [router to server]
reply goes:
192.168.1.76 > router.LAN.IP [server to router]
50.99.215.64 > 192.168.1.x [router to client]
OR
You can use an internal recursive DNS server to provide normal DNS resolution and also override the Internet DNS zone for your domain and return the local IP instead.
If the router won't do hairpining and you find running your own recursive DNS systems to not be an option you can, or want to, take...
You can also trick the local systems into using the local IP by modify the hosts file [in each internal system that needs to access the web server], with:
192.168.1.76 maksconsulting.ca