• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.

Running Plesk behind NAT, DNS zone files broken

G

gsinker

Guest
We are running Plesk behind a NAT. As a result all of our domain DNS zone files have changed to use the internal IP address instead of the external one. We changed the DNS template so that it uses the external IP address but it doesn't look like it changes the existing domain zone files.

It looks like there's a fix for the Linux version of Plesk here:
http://kb.odin.com/1984

But there's no equivalent for Windows. We have over 500 domain files to modify which is going to be very time consuming. Is there a similar fix for the Windows version of Plesk or a script we can run to fix it?
 
But there's no equivalent for Windows. We have over 500 domain files to modify which is going to be very time consuming. Is there a similar fix for the Windows version of Plesk or a script we can run to fix it? http://methoo.com
 
Back
Top