I flipping knew it! The second I started typing it up. I realized that even if the request hit's the server. The DNS is going to give up an internal address that's useless to the browser. FUDGE! I don't know what I was thinking. So noobish of me.aks wrote:Hmmm, I don't think that'll work as the traffic from the web server will have a source of <private IP>, so the originator can't reply to the message(s).
I think what you want is a reverse proxy.
All traffic inbound hits the proxy and the proxy forwards the request (based on say the URL) to the responsible web server. The web server replies to the proxy and the proxy forwards that onto the client. As the proxy is Internet facing, the originator can simply reply to the proxy (who will forward the request to the web server as before).
How you go about that depends on what proxy you choose to use (many people use Nginx, Apache HTTPd, Apache Traffic Manager and so on - there are many to choose from).
I'm using a server running HTTPd, hosting one(1) of my domains. Can I configure it to send the http/ https/ ftp/ request to another server hosting my other two(2) domains?