• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Install behind firewall / dns setup

T

timberman_r

Guest
I am getting ready to deploy plesk to 2 servers and have a question on DNS setup. How does the DNS get controlled as I will have private IP's on the inside and Public on the outside of the firewall. I see nothing in the online documentation saying this can even be done.


Thanks!
Russ
 
I have just completed this same thing with public IP's.
I had to use IPmaps in the router to map the public to private and bridged 1 public through the router/bridge.
From the private side I see the private IP's only on the private side and public as from any other net.

Hope this helps.
 
ouch

boy how many IP's did you have to do on this?
Sounds very tedious. But I'll look into it.

Thanks for the reply!

Russ
 
Have the servers use internal addresses, but have the dns setup for the sites with the external IP of the website/server. These are the records that will be propagated. The problem I ran into during testing though with 6.5 is that bind's config is lacking the commands needed to force it to forward requsts via port 53, so nothing was updating (even after adding the config lines). I don't have this problem with the PSA6 or 7, or windows DNS.
 
Back
Top