Lab 4 - HTTP and Apache

Name: ___________________________________

For this lab you can use the Linux server as a client or, better yet, use a Windows client if you have a hard drive from another class that you can use.

1. Make sure your DNS is setup to resolve both www.yourdomain.com and www1.yourdomain.com to your IP address. (yourdomain.com should be replaced with the domain name you setup in Lab 3)

2a. If you are using your Linux server as your client, add the following line to your /etc/resolv.conf file before the current namserver line: 

nameserver 127.0.0.1
If you are using another Linux system, set the IP to the IP address of your server.

2b. If you are using a Windows computer as your client, add your Linux server's IP address as the first DNS server. (You can find your IP address with the ifconfig command.

3. Look at the /etc/httpd/conf/httpd.conf file and make any changes that are required to have apache respond to www.yourdomain.com. You probably don't need to make any but you should always change the ServerAdmin root@localhost line to contain your real email address.

4. Set Apache (httpd) to start automatically at boot up.

5. Start httpd with the default settings.

6. Check that both names are working with mozilla. (You can start mozilla by typing mozilla at the command prompt. If X-Windows is not running, you must run startx first.)

7. Now set up apache so that it delivers www1.yourdomain.com as a virtual host.

8. Have your server checked by the instructor.

Hints:

a) You will need to create a directory with an index.html file for one of your virtual hosts. Make sure the page is different so that you can see that it is working.

b) your new directory, and its parent directories, will have to have execute permission for the apache user.

c) You set the virtual host information in Part 3 (at the end) of the httpd.conf file. You need a seperate <VirtualHost *> section for each virtual host you set up. You will also need to uncomment the NameVirtualHost * line.

d) If you get errors when starting apache, a possible problem is some conflicting configuration in the file /etc/httpd/conf.d/ssl.config. Just rename it to ssl.config.orig (or anything without the .config at the end) so it will not be included.