• Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Plesk behind NAT (DNS problems)

M

mlnospam

Guest
Hello,

All our internet servers are actually located on a private IP range behind a firewall doing NAT. So this is also the case for our newly installed Plesk 8.2 server. The problem is that Plesk uses it's interal private IP address for creating DNS zones :(

So actually I was wondering if using Plesk/Expand behind NAT on a private IP range is a bad practice ? And if not how can I cope with the DNS issue ?

I couldn't find any kind of "plesk behind NAT howto"...

Many thanks
Regards
 
Take a look at the swsoft knowlegebase article:
http://kb.swsoft.com/en/1984
Generally there is no any howto as Plesk does not have (yet) any mechanism to automatically configure the servers behind NAT. You should change everything manually.
 
Thanks Monica for your answer. I have now changed my DNS zone template to use the external IP address instead of just <ip> and so far it works. The only problem which I can't resolve right now is that the secondary DNS server (slave) for that zone get's configured with a private IP address for it's master, so it cannot synch.

Here is the entry in /var/named/run-root/var/named/slave_zones on our secondary DNS server:

zone "mydomain.tld" {
type slave;
file "slaves/mydomain.tld";
masters {
192.168.100.96;
};
};

Do I also have to manually change this or is there a automatic way ?

Btw we use centralized DNS servers with Plesk Expand.

Thanks
 
Back
Top