... and other essential ports 20000 (usermin), 22 (SSH) etc.

When you have gotten everything running and are more familiar with which specific ports you need to use, then restrict port access via your router admin interface again.

Thanks again A H.

Create New Virtual Server jrdezine.com first, then ns9.jrdezine.com, ns10.jrdezine.com and adelfieds.com, in
that sequence.

DONE

The IP address you should use when creating the websites is 10.1.1.3

DONE

After creating the website with Virtualmin Pro, your website home directories will be created here:

CORRECT

/home/jrdezine.com/public_html/
/home/ns9.jrdezine.com/public_html/
/home/ns10.jrdezine.com/public_html/
/home/adelfieds.com/public_html/

See if you can access jrdezine.com and the other 3 websites now.

ONLY FROM SERVER

You won't be able to "see" your websites if you have not configured your DNS correctly on your server. Check the Administrator's Guide via] Support] Documentation link on this website for instructions on DNS.

NO LUCK

Good luck.
THANKS BUT... :o(

dmz 10.1.1.3
Maybe4 time for a support ticket methinks?

Hi Justin,

I don't use my own server as a name server, so I can't tell you much in great details as to what to do on your server.

But the entries you definitely need in your DNS record for each of your domain names are:

HOST TYPE MAP
---- ---- ---

@ A 150.101.247.226
www A 150.101.247.226
mail A 150.101.247.226
ns9 A 150.101.247.226
ns10 A 150.101.247.226
@ MX 25 mail
@ NS ns9.jrdezine.com
@ NS ns10.jrdezine.com

For the other domain names, you don't need to include the lines starting with ns9 and ns10.

There are free DNS services around. Just google "free DNS" and you will find a few. I personally prefer not to host DNS on my server because if my server is down, I would like to be able to quickly redirect my domain name to another server very quickly. If I have my DNS elsewhere, I just need to change the IP address of the record I mentioned above and I'm back in business.

They say they will compile PHP with mcrypt in the next major release... when is that is anybody's guess.

It's rolling into some repositories this weekend (already in FC6 and FC5, though I haven't rsync'ed it over yet, as it hasn't been tested much yet). CentOS will also probably come by Monday.

Justin is running Ubuntu, which provides the php mcrypt packages in universe (i.e. he doesn't have to wait for our packages to support it).

See if you can access jrdezine.com and the other 3 websites now.

ONLY FROM SERVER

This indicates, as A H has indicated, that DNS isn't spinning right. It can also indicate that your router doesn't actually route (most consumer routers cannot perform NAT on traffic coming from the internal network back to the internal network--so if your router is deficient in this way, you'll run into further troubles). DNS is tricky on multiple counts, but is fixable.

The first piece of trouble for you is my fault. I was too tired last night when I configured your box to remember to set it up for private network usage. Your DNS records need to point to your public IP address, and not the internal IP address. This needs to be set in the Module Configuration under Other Server Configuration. Find the option labeled "Default IP address for DNS records" and set it to your public IP address (don't change any others, as the Apache config needs to have the private address! If you're on a dynamic IP, you may instead want to use the Dynamic IP Update feature--this allows you to use DynDNS.org to maintain your DNS records.

Also note that just changing the IP in the configuration won't update the existing DNS records. They can be changed in the Services:DNS Options page for each of your domains.

Next up, you'll need to go to your registrar (wherever you registered your domains) and update them to point to your server (and a secondary server--see our DNS Slave guide for how to setup a secondary DNS server). Or, use one of the existing DNS services (if your IP changes periodically that's your only option).

Finally, if the IP on your system changes (I believe you found it picked up different IPs between when we first talked and when I actually logged in?) all of your Apache VirtualHost/NameVirtualHost configuration will be wrong. You'll want to make sure the private IP for this box doesn't change (changing would also lead to your DMZ not working).

> You'll want to make sure the private IP for this box doesn't change (changing would also lead to your DMZ not working).

To fix a static private IP for your server, you need to do this:

1. Go to your router admin interface, and stipulate 10.1.1.3 is for your server (enter the server's MAC address).

2. You must set your server to use a specific/static IP address (i.e. 10.1.1.3). That is, you cannot have the server obtain an IP address via DHCP each time it boots.

Point 2. above relates to your Network Card eth0 setting.

Justin, continue your questions here... for the sake of continuity and easier referencing...

COPIED OVER:

"Hi all, so far so good thanks heaps for all your help so far (esp, Joe and A H).

I was trying to place an index.html into /var/www/ but couldn't because.. it just wouldn't let me.

I did a sudo chown myUsername /var/www/
it let me place the index file in teh directory however when i go to
http://localhost/ i get 403'd you don't have persmission to access / on this server.

Any help on how to fix this?
( chown root doesnt change anything either) "


For goodness sake, don't chown all the directories to root. This is just bad practice.

After you've created a domain name, use the domain administrator's login via SSH or FTP to

/home/mydomain.com/public_html


VMpro creates home directory to websites in /home not /var/www/html. Your website contents should be in /home/mydomain.com/public_html and not /var/www/html

You have to configure /etc/httpd/conf/httpd.conf

I couldn't tell with the discussion of DNS and what-not if the original problem has been solved yet or not. (Getting the system document root instead of the VServer document root.)

I ran into the same symptom and without any DNS problems, and also noticed a configuration warning from apache when it restarts (although I don't remember now what it was.) I solved this by using the specific IP address in the Virtual Server config. To do this in Virtualmin select the VServer in question, and then Services and then Configure Website. This will take you to the Webmin page for the virutal server. Near the bottom there is a Virtual Server Details: Address field that probably has "Any" selected. Select the next radio item instead and put the IP address in the field. Then click the Save button and then Apply Changes on the next page. You may have to do this for all the virtual servers except for the default ones before they all start working properly.