cvs commit: src/etc/namedb PROTO.localhost-v6.rev PROTO.localhost.rev make-localhost named.conf src/etc/namedb/master empty.db localhost-forward.db localhost-reverse.db

[Doug Barton]

dougb       2007-06-18 05:58:23 UTC

  FreeBSD src repository

  Modified files:
    etc/namedb           named.conf 
  Added files:
    etc/namedb/master    empty.db localhost-forward.db 
                         localhost-reverse.db 
  Removed files:
    etc/namedb           PROTO.localhost-v6.rev 
                         PROTO.localhost.rev make-localhost 
  Log:
  Bring our default named configuration more in line with current
  best practices:
  
  1. The old way of generating the localhost zones was not optimal both
  because they did not exist by default, and because they were not really
  aligned with BCP. There is no need to have the dynamic data that the
  make-localhost script generated, and good reasons to do this more
  "by the book."
  
  2. In named.conf
          a. Clean up white space
          b. Add/clarify a few comments
          c. Slave zones from the root servers instead of using a hints
          file. This has several advantages, as described in the comments.
          d. Significantly revamp the default zones, including the
          forward localhost zone, and the reverse zones for IPv4 and IPv6
          loopback addresses. There are extensive comments describing what
          is included and why. Interested readers should take the time to
          review the RFCs mentioned in the comments. There is also relevant
          information about the motivations for hosting these zones in the
          "work in progress" Internet-Draft,
          http://www.ietf.org/internet-drafts/draft-ietf-dnsop-default-local-zones-02.txt
          or its successor.
          It's also worth noting that a significant number of these
          empty zones are already included by default in the named binary
          without any user configuration.
          e. Because we're including a lot of examples of both local
          forward zones and slave zones in the default configuration,
          eliminate some of those examples.
  
  3. Add new localhost-{forward|reverse} zone files, and an "empty" zone
  to support the changes in 2.d. above. The empty zone file isn't really
  empty in order to avoid a warning from BIND about a zone file that
  doesn't contain any A or AAAA records.
  
  Revision  Changes    Path
  1.2       +0 -17     src/etc/namedb/PROTO.localhost-v6.rev (dead)
  1.7       +0 -17     src/etc/namedb/PROTO.localhost.rev (dead)
  1.8       +0 -49     src/etc/namedb/make-localhost (dead)
  1.1       +11 -0     src/etc/namedb/master/empty.db (new)
  1.1       +11 -0     src/etc/namedb/master/localhost-forward.db (new)
  1.1       +13 -0     src/etc/namedb/master/localhost-reverse.db (new)
  1.23      +180 -36   src/etc/namedb/named.conf