From owner-freebsd-hackers  Tue May  6 16:32:56 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA13288
          for hackers-outgoing; Tue, 6 May 1997 16:32:56 -0700 (PDT)
Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA13281
          for <freebsd-hackers@freebsd.org>; Tue, 6 May 1997 16:32:47 -0700 (PDT)
Received: from awfulhak.demon.co.uk (localhost.lan.awfulhak.org [127.0.0.1])
	by awfulhak.demon.co.uk (8.8.5/8.8.5) with ESMTP id AAA13884;
	Wed, 7 May 1997 00:32:25 +0100 (BST)
Message-Id: <199705062332.AAA13884@awfulhak.demon.co.uk>
X-Mailer: exmh version 1.6.9 8/22/96
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
cc: freebsd-hackers@freebsd.org
Subject: Re: bind before hosts and iijppp... 
In-reply-to: Your message of "Tue, 06 May 1997 20:12:21 +0200."
             <19970506201221.SY61854@uriah.heep.sax.de> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 07 May 1997 00:32:25 +0100
From: Brian Somers <brian@awfulhak.org>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> As Brian Somers wrote:
> 
> > > Too many people might playingly enable this entry then, it's not a
> > > good idea.  Maybe a secondary for `domain.com'. :-)
> > 
> > Agreed.  I also think a "cheat entry" should be made available, but
> > I wouldn't mind some comments on this.
> 
> What about this:
> 
> ; Example secondary config entries.  It can be convenient to become
> ; a secondary at least for the zone where your own domain is in.  Ask
> ; your network administrator for the IP address of the responsible
> ; primary.
> ;
> ; Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
> ; (This is the first bytes of the respective IP address, in reverse
> ; order, with ".IN-ADDR.ARPA" appended.)
> ;
> ; Before starting to setup a primary zone, better make sure you fully
> ; understand how DNS and BIND works, however.  There are sometimes
> ; unobvious pitfalls.  Setting up a secondary is comparably simpler.
> ;
> ; NB: Don't blindly comment out the examples below. :-)  Use actual
                              ^^^
                              Don't you mean "in" ?

> ; names and addresses instead.
> ;
> ;type       zone name               IP of primary  backup file name
> ;==================================================================
> ;secondary  domain.com              127.0.0.1      domain.com.bak
> ;secondary  0.168.192.in-addr.arpa  127.0.0.1      0.168.192.in-addr.arpa.bak
> ;
> ;
> ; If you've got a DNS server around at your upstream provider, enter
> ; its IP address here.  This will make you benefit from its cache,
> ; thus reduce overall DNS traffic in the Internet.
> ;
> ;forwarders 127.0.0.1

; If you don't wish to do any DNS searches yourself, use the following
; line to force all non-primary and non-secondary lookups to go to your
; forwarders.  You should point your forwarders line at one or more caching
; DNSs if you use this.
options forward-only

> -- 
> cheers, J"org
> 
> joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
> Never trust an operating system you don't have sources for. ;-)

-- 
Brian <brian@awfulhak.org>, <brian@freebsd.org>
      <http://www.awfulhak.org>
Don't _EVER_ lose your sense of humour....