From: Mark Andrews <marka@isc.org>
Date: Wed, 2 Nov 2005 22:53:51 +0000 (+0000)
Subject: extend cname and other data answer
X-Git-Tag: v9.3.2rc1~12
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=846d6beed8fd37e611a1cd7bad05b17880e8f7ce;p=thirdparty%2Fbind9.git

extend cname and other data answer
---

diff --git a/FAQ.xml b/FAQ.xml
index a732ff60433..963cd0a8c40 100644
--- a/FAQ.xml
+++ b/FAQ.xml
@@ -17,7 +17,7 @@
  - PERFORMANCE OF THIS SOFTWARE.
 -->
 
-<!-- $Id: FAQ.xml,v 1.4.6.2 2005/09/06 02:58:40 marka Exp $ -->
+<!-- $Id: FAQ.xml,v 1.4.6.3 2005/11/02 22:53:51 marka Exp $ -->
 
 <article class="faq">
   <title>Frequently Asked Questions about BIND 9</title>
@@ -602,6 +602,17 @@ rand_irqs="3 14 15"</programlisting>
 dig axfr example.com @master-server &gt; tmp
 named-checkzone example.com tmp</programlisting>
 	</informalexample>
+	<para>
+	  A CNAME record cannot exist with the same name as another record
+	  except for the DNSSEC records which prove its existance (NSEC).
+	</para>
+	<para>
+	  RFC 1034, Section 3.6.2: <quote>If a CNAME RR is present at a node,
+	  no other data should be present; this ensures that the data for a
+	  canonical name and its aliases cannot be different.  This rule also
+	  insures that a cached CNAME can be used without checking with an
+	  authoritative server for other RR types.</quote>
+	</para>
       </answer>
     </qandaentry>