order as the <CODE>VirtualHost</CODE> directives appear in the config
file.
-<P>The first vhost on this list (the first vhost that appears after the
-corresponding <CODE>NameVirtualHost</CODE> directive in the config file)
-has the highest priority and catches any request to an unknown
-server name or a request without a <CODE>Host:</CODE> header.
+<P>The first vhost on this list (the first vhost in the config file with
+the specified IP address) has the highest priority and catches any request
+to an unknown server name or a request without a <CODE>Host:</CODE>
+header.
<P>If the client provided a <CODE>Host:</CODE> header the list is
searched for a matching vhost and the first hit on a <CODE>ServerName</CODE>
<SAMP>www.domain.tld</SAMP> is an alias (CNAME) pointing to the IP address
<SAMP>111.22.33.44</SAMP></P>
+<p>Note: When you specify an IP address in a <code>NameVirtualHost</code>
+directive then requests to that IP address will only ever be served
+by matching <VirtualHost>s. The "main server" will <b>never</b>
+be served from the specified IP address.
+
<P>Additionally, many servers may wish to be accessible by more than
one name. For example, the example server might want to be accessible
as <CODE>domain.tld</CODE>, or <CODE>www2.domain.tld</CODE>, assuming
<SAMP>www.domain.tld</SAMP> is an alias (CNAME) pointing to the IP address
<SAMP>111.22.33.44</SAMP></P>
+<p>Note: When you specify an IP address in a <code>NameVirtualHost</code>
+directive then requests to that IP address will only ever be served
+by matching <VirtualHost>s. The "main server" will <b>never</b>
+be served from the specified IP address.
+
<P>Additionally, many servers may wish to be accessible by more than
one name. For example, the example server might want to be accessible
as <CODE>domain.tld</CODE>, or <CODE>www2.domain.tld</CODE>, assuming