# ...<br />
</VirtualHost>
</example>
+
+ <p>Name-based virtual hosts for the best-matching set of <directive
+ type="section" module="core">virtualhost</directive>s are processsed
+ in the order they appear in the configuration. The first matching <directive
+ module="core">ServerName</directive> or <directive module="core"
+ >ServerAlias</directive> is used, with no different precedence for wildcards
+ (nor for ServerName vs. ServerAlias). </p>
</usage>
<seealso><directive module="core">UseCanonicalName</directive></seealso>
<seealso><a href="../vhosts/">Apache HTTP Server Virtual Host documentation</a></seealso>
<indent>
# This first-listed virtual host is also the default for *:80
ServerName www.example.com<br />
- ServerAlias example.com *.example.com<br />
+ ServerAlias example.com <br />
DocumentRoot /www/domain<br />
</indent>
</VirtualHost><br />
first have your DNS server properly configured to map those names to an IP
address associated with your server.</p>
+ <p>Name-based virtual hosts for the best-matching set of <directive
+ type="section" module="core">virtualhost</directive>s are processsed
+ in the order they appear in the configuration. The first matching <directive
+ module="core">ServerName</directive> or <directive module="core"
+ >ServerAlias</directive> is used, with no different precedence for wildcards
+ (nor for ServerName vs. ServerAlias). </p>
+
<p>Finally, you can fine-tune the configuration of the virtual hosts
by placing other directives inside the <directive type="section"
module="core">VirtualHost</directive> containers. Most directives can be