ispconfig3 Multiple Sites (Domains) in one Server

Discussion in 'General' started by dcarlos, Mar 14, 2009.

  1. till

    till Super Moderator

    Which exact ISPConfig release? There was such a bug in one of the older releases, you should update to 3.0.1.4
     
  2. dclardy

    dclardy New Member

    I am working on that as we speak. I am switching to Debian so we will see how it goes.

    Thanks.
     
  3. tomnhanni

    tomnhanni New Member

    I'm having these same issues.

    This is a headless test system which I'm remotely admining. Currently there are no DNS-A records pointing to this machine because I'm planing to move my clients domains to this server if all goes well with ispconfig3.

    Suse 11.1

    I have 2 clients and each has its own test domain set up.

    The hostname of the machine is ie. hostname.com so I want to set up subdomains for testing

    client 1 has client1.hostname.com

    client 2 has client2.hostname.com

    so I checked the sites-available directory and the doc roots are all ok:
    client1: --> DocumentRoot /srv/www/client1.hostname.com/web
    client2: --> DocumentRoot /srv/www/client2.hostname.com/web

    but it still resolves to the first client1 directory and no matter what I type.

    ie. http://foo.hostname.com still shows the content from client1 this is frustrating. It is ignoring what i put as documentroot and only resolving the last client that i set up.

    Is there some way to test this without having real domains attached to this machine? What I want to do is have all my clients set up with content and fake domains and when I'm ready just move the domain records to my new machine and then just change the domain settings in ispconfig3.
     
  4. tomnhanni

    tomnhanni New Member

    So i think I figured this one out...

    I just made some sites with fake domains then I have to go and manually edit the corresponding sites-available .vhost file and change the ServerName to client1.hostname.com then it works....

    The only trouble is everytime I use ispconfig3 to edit a website it writes over my changes in the .vhost file. ::mad:
     
  5. giftsnake

    giftsnake New Member

    is there an A record for every subdomain?
    is e.g. client1.hostname.com the content of the field 'domain' in the sites tab?

    maybe autosubdomain *. is activated for hostname.com?
     
  6. tomnhanni

    tomnhanni New Member

    The problem is the real domains are running on a different production server.

    So I want to set up temporary domains or subdomains on the new box test it out and then tell my ISP to move the domains over to the new box as soon as I'm ready. This is to have little or no downtime.

    So what I've done now is go ahead and use the real domains in the sites tab.

    This ofcourse wont work because the domains resolve to my other server IP.

    So like I said I got it work by maually adding the ServerName in .vhost like this

    real-domain.newhost.com which works great.

    But ispconfig3 likes to overwrite my manual changes everytime i edit the site in sites tab.

    Maybe this helps anyone testing out a new server before moving.
     
  7. giftsnake

    giftsnake New Member

    did you create the A record on the productionmachine with the ip from your testbox?

    why not use the 'automatic' functions in ispconfig? i dont think it's neccessary to manipulate the vhostfiles...
     
    Last edited: Sep 11, 2009
  8. tomnhanni

    tomnhanni New Member

    I think you are talking about a redirect(I'm still learning all this stuff) if I do that then the domains won't be available on the production machine anymore or? This is bad if something goes wrong on the testmachine...I have to move over 100 domains copying files and MySql databases so it might take some time and possible even some reinstalls if I mess something up. After the 100 domains are setup on the new server I give my ISP the goahead and they move the A records over to my new machine and kill the old box.

    So now you see why I have to manually mess with the vhost files.
     
  9. giftsnake

    giftsnake New Member

    am i correct in thinkin: you have a domain domain.com on productionmachine and want to move it to testbox, but it should still be available on productionmachine?

    maybe you can try this:
    create A record with ip from testbox on productionmachine
    create aliasdomain for every domain on testbox

    no redirect.
     
  10. tomnhanni

    tomnhanni New Member

    Well that might work but I am not able to create an A record from my production box to a different IP. Only options are redirects so then my domain wont be reachable on the original production box.

    But I think this works quite well what I have now.

    in ispconfig3 sites tab --> add new website

    as domain mydomain.com (the real one)

    of course this is not reachable in the browser just the production box.

    Then i go in and edit the .vhost file for the mydomain.com on my test box and change the entry ServerName to something like mydomain.testboxhostname.com and I get the test mydomain.com website. Later after my ISP has changed the A record to my test box IP i have to go back and edit the vhost file to ServerName mydomain.com or just save the settings in ispconfig3 and it will write the correct ServerName.
     

Share This Page