• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

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