I have 4 public IPs that are being used on my system and are properly configured in ifcfg-eth0 through ifcfg-eth0:3. I have create ns1 and ns2 successfully and bind is running. I have created a web site on the same IP as ns1. When I access the unused IPs I get the fedora test page. When I access the ip address for the web site I get the shared ip page!? Checking Vhosts_ispconfig.conf the named virtual host is set to the same IP as the web site. Hence the shared IP page. Now, the question is.. Can I manually change the IP for named virtual hosts to correct this problem? And, can I manually change the document root for the web site to it's proper /var/www/www.website.com directory (which was created by ispconfig?. Or is there some easy fix I'm overlooking?
You can change the IP of the ISPConfig Server in the admin tool under "Management/Settings" To change the IPs for the individual domains go to their settings under ISP Manager. I don't recommend to change the IPs manually because ISPConfig overwrites your changes. I guess you could copy/move the files to the directory you wish and change the document root under "Management/Settings/Web". Though I never tested this.
Thanks for the reply. This one is driving me nuts. Just for the heck of it I added another dedicated site on a totally unused IP and now it too is being listed as a shared IP. It seems all IP addresses are being created as shared IPs. I do find it odd that there is no choice in ISPConfig to dedicate an IP to a web site or make it shared.
As you concluded yourself: all IP's are shared, until the admin decides (and guards) to use one IP only for one site. If you "forget you assigned a specific IP to one site, you can easily end up with a shared IP. the shared IP page will go away if you define your site. However, accessing the domain/site by it's IP address will always return the shared IP page. ISPConfig could be enhanced with this. I'd consider this a RFE
Well, I suppose I could change the nameserver IPs for one domain and see if they everything works correctly. Using the IP address to access a site before it goes live is pretty common. I had hoped to do this since I'll be moving 3 active sites from a leased server to our own in house server. All in all, except for this little glitch I'm very impressed with ISPConfig so far.
If you are authoritative for a domain (I am at least for my own ISP company) and control your nameservers, you can easely create a temp dns entry and add that as a co-domain. So in DNSmanager I add a record "customer.myispdomain.tld" and have that point to the dedicated IP. In siteadmin, I create the site as it should be: "www.customerdomain.tld" and add a co-domain "customer.myispdomain.tld". Works great, but a little extra work. You only need to allow for one extra domain in your specification for a customer.
I have one domain that isn't really critical to anything so I just changed the name servers for that. The new name servers are showing up (DNS Report) and operating correctly and I just need to wait for the change to propagate to be sure everything is hunky dory. The only problem I'm having now has to do with the server name appearing in the ehlo (host greeting). I knew how to get around that in Plesk, but that's going to be a different topic here.
