![]() The idea, was to tunnel the webserver as a client to the AWS EC2 Openvpn Access Server instance for the sole purpose of using and AWS IP address, DNS address, and setting the proper PTR Records on amazons elastic IP's settings. In an attempt to solve this, I have created a cloud AWS Openvpn Access Server EC2 Instance, and have assigned it an elastic IP, which now has the proper PTR and reverse DNS records for my server. My issues is that my home IP is a not a static IP, so I cannot set the proper Reverse DNS and PTR records for the email server. To get all of the email/web server ports working, I had to forward port 443, port 80, and the corresponding email server ports, from my 'ISP router' to my 'firewall router', then, forward those same ports from my 'firewall router' to my 'LEMP Webserver'. ![]() I believe this would be called a double NAT setup. My server is behind a firewall router, which is behind my ISP router. I have successfully set up a LEMP email/webserver running off of my home IP address, with my domains dns pointing to my home IP.
0 Comments
Leave a Reply. |