• 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Public IP on private plesk server

Z

zaidee

Guest
I have problem in setting the domain ip address. My plesk server is running private ip which behind firewall and the public IP is translate using NAT. After setting up the domain using the physical ip, let say 192.168.1.2, the DNS of the domain is taking the physical ip as DNS records. I have to change back to DNS record to public IP in order for the domain to be resolved by public users. Whenever I create a new subdomain, the subdomain will take physical ip not the public IP. I have placed the public Ip in the client IP pool. Can anybody help me.
 
You must log in or register to reply here.

Similar threads

V
Question Plesk behind nat and multiples public ip adress
Replies
7
Views
1K
ExPx
E
F
Question IPv4 forwarding rule
Replies
8
Views
401
alvarezcruz
alvarezcruz
Talistech
Resolved Bug? Plesk NAT uses internal ip for subdomains instead of public IP
Replies
8
Views
1K
Sebahat.hadzhi
Sebahat.hadzhi
Talistech
Resolved Bug: Plesk NAT - IP Reset via command line does not work because plesk things the ip does not exist.
Replies
3
Views
924
Talistech
Talistech
R
Resolved Plesk API key not working
Replies
2
Views
1K
Kaspar@Plesk
Kaspar@Plesk
Back
Top