documented new treatment of undefined TTLs in zone files

diff --git a/FAQ b/FAQ
index 80b33208beebc47b726919de6e76d3452875196b..c677910169fcdeb66f6e927aeec280eed82b8d99 100644 (file)
--- a/FAQ
+++ b/FAQ
@@ -27,10 +27,11 @@ of a security risk than a root process that has not dropped privileges.
 version to be built, which will allow -u to be used.
 
 
-Q: Why does named log the error message "no TTL specified" and refuse
-to load my zone file?
+Q: Why does named log the warning message "no TTL specified - using SOA
+MINTTL instead"?
 
-A: Your zone file must either have a line like
+A: Your zone file is illegal according to RFC1035.  It must either
+have a line like
 
    $TTL 86400
 
@@ -39,9 +40,6 @@ like the "84600" in this example:
 
    example.com. 86400 IN SOA ns hostmaster ( 1 3600 1800 1814400 3600 )
 
-BIND 8 incorrectly accepted files that had neither.
-
-
 Q: Why do I see 5 (or more) copies of named on Linux?
 
 A: Linux threads each show up as a process under ps.  The approximate

diff --git a/doc/misc/migration b/doc/misc/migration
index d6a6c08333a9994ed4fcfe1814901578f65ef252..0fdb682774ac560776bbc35a74aec056cec8aa65 100644 (file)
--- a/doc/misc/migration
+++ b/doc/misc/migration
@@ -63,17 +63,26 @@ Multiple classes have to be put into explicit views for each class.
 
 2.1. Strict RFC1035 Interpretation of TTLs in Zone Files
 
-BIND 8 allowed you to omit all TTLs from a zone file, and used the
-value of the SOA MINTTL field as a default for missing TTL values.
+BIND 9 strictly complies with the RFC1035 and RFC2308 rules regarding
+omitted TTLs in zone files.  Omitted TTLs are replaced by the value
+specified with the $TTL directive, or by the previous explicit TTL if
+there is no $TTL directive.
 
-BIND 9 enforces strict compliance with the RFC1035 and RFC2308 TTL
-rules.  The default TTL is the value specified with the $TTL
-directive, or the previous explicit TTL if there is no $TTL directive.
 If there is no $TTL directive and the first RR in the file does not
-have an explicit TTL field, the error message "no TTL specified" is
-logged and loading the zone file fails.
+have an explicit TTL field, the zone file is illegal according to
+RFC1035 since the TTL of the first RR is undefined.  Unfortunately,
+BIND 4 and many versions of BIND 8 accept such files without warning
+and use the value of the SOA MINTTL field as a default for missing TTL
+values.
 
-To avoid problems, use a $TTL directive in each zone file.
+BIND 9.0 and 9.1 completely refused to load such files.  BIND 9.2
+emulates the nonstandard BIND 4/8 SOA MINTTL behavior and loads the
+files anyway (provided the SOA is the first record in the file), but
+will issue the warning message "no TTL specified; using SOA MINTTL
+instad".
+
+To avoid problems, we recommend that you use a $TTL directive in each
+zone file.
 
 2.2. Periods in SOA Serial Numbers Deprecated
 
@@ -208,4 +217,4 @@ directing queries for a given domain to a particular set of name
 servers.
 
 
-$Id: migration,v 1.32 2001/05/19 01:29:12 gson Exp $
+$Id: migration,v 1.33 2001/05/22 02:01:28 gson Exp $