First timer! Need help with configuration

J

jim.thornton

Verified User
Joined
Jan 1, 2008
Messages
334
Hey There... Looking to get some help with DA. This is the first time that I have owned a VPS and the first time that I have used DirectAdmin.

I just bought this VPS and the provider installed DA with the vps.

I'm running:
CentOS 5
Apache 2.2.6
PHP 5
MySQL 5
384MB (1GB Burstable)
20G
300G bandwidth

I have a few questions:

1. I've been getting help from someone to secure the server, and everything is done, except, I have to install mod security still. However, while this person was helping me set it up, we logged in under the admin user that was setup from the vps provider's install. Within this account we setup DNS record for my domain.com. Then I tried to go to the user tab of the admin user so that I could create an email address [email protected] and there was nothing there (it said 'add domain' or something). I tried adding my domain.com and it said it failed because the domain already existed. So... I deleted the DNS record for domain.com and created a Reseller account instead - 'Reseller1'.

I then logged in under the 'Reseller1' user and I was able to add the email address like I was told.

- Was this the correct way to configure it?

2. When I was in the new Reseller1 account, I discovered an error in the apache error log and I don't know what it means or why it is there:

[Tue Jan 01 23:37:04 2008] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?

I don't understand why it says 'localhost' because I changed the hostname for my server (ie. www1.domain.com from localhost).

- What is this error from and why is it there?

3. With my server I purchased 4 IP's. Let's say they are 192.168.1.1 - 192.168.1.4. Here is what I want:

1 domain.com (Reseller1 account mentioned earlier) - main site which will sell hosting & reseller plans (this site will need a dedicated IP because it will require SSL).

2 reseller.com - this is a site I will create to sell discount hosting service dedicated IP.

3 reseller2.com - this is a site I will create to sell full service hosting service dedicated IP.

4 personalsite1.com - this is a personal site that will require dedicated IP

5 personalsite2.com - this can be shared

6 personalsite3.com - this can be shared

7 personalsite4.com - this can be shared

---> This setup is an ultimate goal and I know that I don't have enough IP's right now. I'll add some IP's as I go. Right now, I'm interested in have #1, 2 and 4 going. So, as these three sites will all require a dedicated IP for the SSL certs, am I okay?

Can I run ns1.domain.com, ftp.domain.com, www1.domain.com, mail.domain.com all off 192.168.1.1 (including the SSL), ns2.domain.com off of 192.168.1.2. And... then run #2 (with SSL) off of 192.168.1.2) and then #4 off 192.168.1.3 (including SSL). Then... All the shared accounts off 192.168.1.4?

Is this possible? Or.. Do I have to configure it another way?
 
zincoxide said:
there was nothing there (it said 'add domain' or something).
Click to expand...
Normal. There's no domain unless you add one.
I tried adding my domain.com and it said it failed because the domain already existed. So... I deleted the DNS record for domain.com and created a Reseller account instead - 'Reseller1'.
Click to expand...
The problem was the DNS zone. Why did the zone exist? Is your server hostname the same as your domain name? If so use DirectAdmin to change it; it'll cause many problems with email down the road.
I then logged in under the 'Reseller1' user and I was able to add the email address like I was told.

- Was this the correct way to configure it?
Click to expand...
It works. Setting up the domain under the User control panel for admin would have worked as well once you deleted the DNS zone file. See my notes above about the hostname problem.
2. When I was in the new Reseller1 account, I discovered an error in the apache error log and I don't know what it means or why it is there:

[Tue Jan 01 23:37:04 2008] [warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?

I don't understand why it says 'localhost' because I changed the hostname for my server (ie. www1.domain.com from localhost).

- What is this error from and why is it there?
Click to expand...
The server name (see my notes above) should NOT be the same as a domain name. If your domain name is example.com, then the server name should NOT be either example.com or www.example.com. server.example.com would be acceptable.

Is the mesage an error or a warning? If a warning, it's probably not important. To correct it you'll need to either create your own cert or buy and install one.
3. With my server I purchased 4 IP's. Let's say they are 192.168.1.1 - 192.168.1.4. Here is what I want:

1 domain.com (Reseller1 account mentioned earlier) - main site which will sell hosting & reseller plans (this site will need a dedicated IP because it will require SSL).

2 reseller.com - this is a site I will create to sell discount hosting service dedicated IP.

3 reseller2.com - this is a site I will create to sell full service hosting service dedicated IP.

4 personalsite1.com - this is a personal site that will require dedicated IP

5 personalsite2.com - this can be shared

6 personalsite3.com - this can be shared

7 personalsite4.com - this can be shared

---> This setup is an ultimate goal and I know that I don't have enough IP's right now. I'll add some IP's as I go. Right now, I'm interested in have #1, 2 and 4 going. So, as these three sites will all require a dedicated IP for the SSL certs, am I okay?

Can I run ns1.domain.com, ftp.domain.com, www1.domain.com, mail.domain.com all off 192.168.1.1 (including the SSL), ns2.domain.com off of 192.168.1.2. And... then run #2 (with SSL) off of 192.168.1.2) and then #4 off 192.168.1.3 (including SSL). Then... All the shared accounts off 192.168.1.4?

Is this possible? Or.. Do I have to configure it another way?
Click to expand...
I haven't studied it, but on the face of it, it looks okay. You really don't have to assign an IP# to a nameserver, you can set nameservers up as virtual nameservers.

Jeff
 
jlasman said:
The problem was the DNS zone. Why did the zone exist? Is your server hostname the same as your domain name?
Click to expand...

My server name is not example.com or www.example.com. It is r1.example.com.

jlasman said:
I haven't studied it, but on the face of it, it looks okay. You really don't have to assign an IP# to a nameserver, you can set nameservers up as virtual nameservers.
Click to expand...

Would you mind explaining how I can setup virtual nameservers please?
 
You must log in or register to reply here.
Back
Top