Article ID: 1984, created on Jun 29, 2007, last review on Jun 17, 2016

  • Applies to:
  • Plesk 12.5 for Linux
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux
  • Plesk 10.4 for Linux/Unix
  • Plesk 12.0 for Windows


Plesk is behind NAT. Plesk Domains are not available. The following warnings are shown when opening a domain in a web browser

Domain name cannot be found


Connection cannot be established


The domain DNS zone is configured incorrectly.


Note: Since Plesk 12, you can use the NAT Manager extension to configure address translation. You can find additional information in the Knowledge Base article #122684: How to configure domain DNS zone if Plesk server is behind NAT.

For older Plesk versions:

  1. Make sure that the real IP address (not the internal one, like 192.168.x.x) is used in the DNS zones for all domains in Plesk.

    To achieve this, change the DNS zones for all domains manually, using:

    Subscriptions > > Open in Control Panel > DNS Settings

    After DNS zones are changed through Plesk, rebuild all DNS zone files using the following command:

    ~# mysql -Ns -uadmin -p`cat /etc/psa/.psa.shadow` -D psa -e 'select name from dns_zone' | awk '{print "/usr/local/psa/admin/sbin/dnsmng --update " $1 }' | sh
  2. Also, update the DNS template with the real IP addresses through Tools & Settings > DNS Template. For example, if the DNS template looks like:

    <domain>.    A    <ip>
    <domain>.    MX (10)    mail.<domain>.
    <ip> / 24    PTR    <domain>.
    ftp.<domain>.    CNAME    <domain>.
    lists.<domain>.    A    <ip>
    mail.<domain>.    A    <ip>
    ns.<domain>.    A    <ip>
    webmail.<domain>.    A    <ip>
  3. Then remove records with a template IP address of <ip> and add new records with the real IP address, for example

    <domain>.    A
    <domain>.    MX (10)    mail.<domain>.
    <ip> / 24    PTR    <domain>.
    ftp.<domain>.    CNAME    <domain>.
    lists.<domain>.    A
    mail.<domain>.    A
    ns.<domain>.    A
    webmail.<domain>.    A
  4. Replace with your actual IP address.

    This causes new domains to be created with the new IP address in the DNS zone.

Search Words

Associate default IP server with the primary plesk domain

Ip address unreacheable via ftp

when adding subdomain , its get the lan ip insted of wan ip

Plesk behind NAT

The domain does not resolve or resolves to another IP address ( Please correct DNS settings.

Ip address unreacheable

DNS Private IP

NAT Manager


plesk email behind firewall

configure DNS zone

web site not working


29d1e90fd304f01e6420fbe60f66f838 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c aea4cd7bfd353ad7a1341a257ad4724a 0a53c5a9ca65a74d37ef5c5eaeb55d7f 01bc4c8cf5b7f01f815a7ada004154a2 e8756e9388aeca36710ac39e739b2b37 dd0611b6086474193d9bf78e2b293040 742559b1631652fadd74764ae8be475e e335d9adf7edffca6a8af8039031a4c7 ed7be2b984f9c27de1d2dc349dc19c6d 85a92ca67f2200d36506862eaa6ed6b8 a766cea0c28e23e978fa78ef81918ab8

Email subscription for changes to this article
Save as PDF