From 9ecd6775445e2fcd31c336691f61c3d6e9620da5 Mon Sep 17 00:00:00 2001
From: Eric Covener <covener@apache.org>
Date: Fri, 5 Jul 2013 15:29:35 +0000
Subject: [PATCH] xform

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1500044 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/vhosts/name-based.html.en | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docs/manual/vhosts/name-based.html.en b/docs/manual/vhosts/name-based.html.en
index 63aea33169..79f7bccbde 100644
--- a/docs/manual/vhosts/name-based.html.en
+++ b/docs/manual/vhosts/name-based.html.en
@@ -111,6 +111,18 @@
         virtual hosts.</p>
     </div>
 
+    <div class="note"><h3>ServerName inheritance</h3>
+       <p> It is best to always explicitly list a  <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> in every name-based virtual host.</p>
+       <p>If a <code class="directive"><a href="../mod/core.html#virtualhost">VirtualHost</a></code> doesn't specify 
+       a <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code>, a server name will be 
+       inherited from the base server configuration.  If no server name was 
+       specified globally, one is detected at startup through reverse DNS resolution
+       of the first listening address.  In either case, this inherited server name
+       will influenced name-based virtual host resolution, so it is best to always
+       explicitly list a  <code class="directive"><a href="../mod/core.html#servername">ServerName</a></code> in every
+       name-based virtual host.</p>
+    </div>
+
     <p>For example, suppose that you are serving the domain
     <code>www.example.com</code> and you wish to add the virtual host
     <code>other.example.com</code>, which points at the same IP address.
-- 
2.40.0