• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • 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.

External DNS maps to IP different from external plesk

J

joshua strebel

Guest
How to get plesk to resolve sites pointed to IP on server but not the same IP delcared in domain webhost setting?

Case example: Client has external DNS and a A record mapped to IP 1.1.1.1, plesk has site on shared IP 1.1.1.1 Everything works.

We need to change 1.1.1.1 in plesk to 2.2.2.2. So under web host settings in plesk we assign this domain to 2.2.2.2.
1.1.1.1 is still a valid ip on the sever, but the domain with A record to 1.1.1.1 no longer resolves.

How do we get the domain to still resolve until the customer updates their A record to the new 2.2.2.2? Seems there is no provision in plesk allow a site to resolve on multiple IP's as a transition period.

Can a NameVirtualHost * be added to a master config file?
Any other ideas?
 
title should be: External DNS maps to IP different from internal plesk IP
 
<VirtualHost *:80>

in http.include works.. or if I create a vhost.conf with <VirtualHost *:80>
and move the Include line out of the <VirtualHost 1.1.1.1:80> block in http.include

This is a localized change though for 1 domain that will be overwritten when plesk rebuilds the files.

How can this be accomplished server wide?
 
Back
Top