1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

External DNS maps to IP different from external plesk

Discussion in 'Plesk 9.x for Linux Issues, Fixes, How-To' started by joshua strebel, Dec 10, 2010.

  1. joshua strebel

    joshua strebel Guest

    0
     
    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?
     
  2. joshua strebel

    joshua strebel Guest

    0
     
    title should be: External DNS maps to IP different from internal plesk IP
     
  3. joshua strebel

    joshua strebel Guest

    0
     
    <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?
     
Loading...