Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Very similar to this question, I just wanted to clarify one thing. If I begin with a vanilla Mac OS X Apache install (using their default httpd.conf file), and then add a named VirtualHost to my apache install, how do I access the files in the original <Directory> directive? Do I need to re-specify the original <Directory> I was using to serve documents as a second named VirtualHost?

share|improve this question
up vote 0 down vote accepted

Yes, your idea is right.

The base configuration acts as a default virtual host if you don't have a vhost matching a connection, so if you're going from 0 vhosts to 1, you might shoot right to two where the first-listed in the set of NVH'es doesn't override the DocumentRoot from the base configuration. The 2nd NVH then has ServerName/ServerAlias for the stuff you actually wanted to be different.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.