Server fqdn and accessing ISPConfig3 Interface Questions

Ok, please bear with me as I'm still an ISPConfig3 newb... I have all of my actual sites/DNS/email setup and running fine through the ISPConfig3 panel.

Here's my situation. I'll use example.com in the place of my real domain. My server's fqdn (hostname -f) is titan.example.com. The short hostname (hostname) is titan. The domain example.com is registered at enom and pointed to my server ip. This results in the standard apache "Welcome" page if you try to access example.com. titan.example.com doesn't actually point anywhere. First, I'd like to get rid of the standard apache site created for example.com. I assume that won't be too difficult.

Second, my work blocks most ports appended to urls, so getting to my control panel without screensharing back to my house by use of ssh tunneling (only port 80 and 443 are open out) is a pretty inconvenient way to access the panel. But, I've been able to access cPanel on my old shared hosting running on port 2082 by using www.oneofmysites.com/cpanel. I'd love to be able to access the ispconfig panel from any of my three main website domains by going to www.oneofmysites.com/ispconfig or something. How difficult is this to accomplish? Is there a guide for this that I've just missed when searching?

Also, it would be great if that would work on my server domain (example.com) as well. While I'm at it, do any of you usually use the fqdn (titan.example.com) for anything? I don't know how I'd do that either.

I'm running on a OpenVZ VPS with 1 GB of RAM, 1 GB of Vswap, and 4 cores. The OS is Ubuntu 12.04 w/Apache/Bind/Dovecot as described int he Perfect Server guide.

Any advice here for this ISPConfig3 newb?

It's amazing to me that I'm a software engineer...I program all day...but DNS stuff still baffles me. I've just run on shared hosting with cPanel for so long. Pretty dang happy with ISPConfig3 so far though. VPS is running well.

Here's my situation. I'll use example.com in the place of my real domain. My server's fqdn (hostname -f) is titan.example.com. The short hostname (hostname) is titan. The domain example.com is registered at enom and pointed to my server ip. This results in the standard apache "Welcome" page if you try to access example.com. titan.example.com doesn't actually point anywhere. First, I'd like to get rid of the standard apache site created for example.com. I assume that won't be too difficult.

Click to expand...

There is no standrad site created for example.com, what you see is the defaut page of apache that is shown when there is no page at all. So all you have to do is to create the website example.com in ispconfig.

Second, my work blocks most ports appended to urls, so getting to my control panel without screensharing back to my house by use of ssh tunneling (only port 80 and 443 are open out) is a pretty inconvenient way to access the panel. But, I've been able to access cPanel on my old shared hosting running on port 2082 by using www.oneofmysites.com/cpanel. I'd love to be able to access the ispconfig panel from any of my three main website domains by going to www.oneofmysites.com/ispconfig or something. How difficult is this to accomplish? Is there a guide for this that I've just missed when searching?

Click to expand...

ISPconfig runs under its own vhost, so you have to use a port to access ist and not a alias. What might work is that you configure a proxy in one of your websites that proxies requests to the ispconfig vhost.

There is no standrad site created for example.com, what you see is the defaut page of apache that is shown when there is no page at all. So all you have to do is to create the website example.com in ispconfig.

Click to expand...

While I agree there is no ISPConfig3 site located at example.com, as far as apache is concerned, there IS a site there. it just loads up whatever is in /var/www. I'd prefer it not do that...just not load anything as if no site exists for example.com. I realize I can just remove the index.html file from /var/www, but how would I go about telling apache to not look there at all?

ISPconfig runs under its own vhost, so you have to use a port to access ist and not a alias. What might work is that you configure a proxy in one of your websites that proxies requests to the ispconfig vhost.

Click to expand...

I understand that it runs under a port, but it would seem that cPanel does the same as it runs on port 2082 at my previous shared hoster. the /cpanel way of getting there didn't appear until the last year or two. I would assume there is a way to do this for ISPConfig3 as well.