Issue Plesk behind NAT uses private IP in DNS records

[maxheadroom]

We are running several plesk servers behind a NAT. On all servers we have the same problem with DNS settings.

After adding a new domain plesk uses the private IP (192.168.xx.xx) for the A record mail.<domain> instead of the puplic IP (62.xx.xx.xx).

The same happens to the A records of subdomains if a customer applys the standard template in the dns settings.
Plesk overwrites the A record of each subdomain with the private IP.

I already tried plesk repair dns but that didn't help.

Anyone any ideas?

 

[MarkM]

I went thru this fun on AWS once. You need to map private -> public IPs.

Running Plesk Behind a Router with NAT

 

[maxheadroom]

Thanks for your answer.
I already mapped the IPs under Tools & Settings -> IP-Adresses.

There has to be another reason for this weird behaviour.

 

[USY]

I went thru this fun on AWS once. You need to map private -> public IPs.

Running Plesk Behind a Router with NAT

Can I map also from CLI because I can’t reach the Plesk login page

 

[IgorG]

Can I map also from CLI because I can’t reach the Plesk login page

#7