• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Plesk 8.2 With NAT

J

JustinK101

Guest
I am using Plesk 8.2 on windows 2003 server x64.

We just purchased a SonicWall TZ180 and I am trying to figure out if this is going to work. Currently I have 3 domains (SHARED) associated with a static ip address (Lets call it 6.6.6.6) assigned via windows tcp/ip static. Now that the SonicWall is here things are going to change, the server is going to get a local ip address (192.168.168.2) via DHCP and NAT is going to handle translating the physical ip address (6.6.6.6) to the private ip address (192.168.168.2).

Will Plesk work with using a private ip address (192.168.168.2) and DNS, FTP, WWW, WWWSSL and everything on my 3 domains work as expected?
 
You need to use private Ips on Plesk and configure external DNS to manage those zones, Plesk DNS cannopt manage external Ips, whiel domains are on private

John S.G.
 
Back
Top