xform

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1500045 13f79535-47bb-0310-9956-ffa450edef68

1 files changed, 12 insertions, 0 deletions

diff --git a/docs/manual/vhosts/name-based.html.en b/docs/manual/vhosts/name-based.html.en
index afc8b25b0b..5bca26c717 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.