From 979207101dbdada6233fd3bb3204a539c00cf9f4 Mon Sep 17 00:00:00 2001 From: peter Date: Mon, 11 May 1998 11:26:28 +0000 Subject: Delete some large chunks of trailing whitespace since it was making some lines longer than 80 columns. --- etc/namedb/named.conf | 32 ++++++++++++++++---------------- 1 file changed, 16 insertions(+), 16 deletions(-) (limited to 'etc/namedb/named.conf') diff --git a/etc/namedb/named.conf b/etc/namedb/named.conf index 8d927c5..31bb075 100644 --- a/etc/namedb/named.conf +++ b/etc/namedb/named.conf @@ -1,5 +1,5 @@ -// $Id: named.boot,v 1.6 1997/05/08 15:23:28 joerg Exp $ -// From: @(#)named.boot 5.1 (Berkeley) 6/30/90 +// $Id: named.conf,v 1.1 1998/05/07 23:42:33 ache Exp $ +// // Refer to the named(8) man page for details. If you are ever going // to setup a primary server, make sure you've understood the hairy // details of how DNS is working. Even with simple mistakes, you can @@ -12,10 +12,10 @@ options { // In addition to the "forwarders" clause, you can force your name // server to never initiate queries of its own, but always ask its // forwarders only, by enabling the following line: -// +// // forward only; -// If you've got a DNS server around at your upstream provider, enter +// If you've got a DNS server around at your upstream provider, enter // its IP address here, and enable the line below. This will make you // benefit from its cache, thus reduce overall DNS traffic in the Internet. /* @@ -44,7 +44,7 @@ host { any; } { // Setting up secondaries is way easier and the rough picture for this // is explained below. -// +// // If you enable a local name server, don't forget to enter 127.0.0.1 // into your /etc/resolv.conf so this server will be queried first. // Also, make sure to enable it in /etc/rc.conf. @@ -61,22 +61,22 @@ zone "0.0.127.IN-ADDR.ARPA" { // NB: Do not use the IP addresses below, they are faked, and only // serve demonstration/documentation purposes! -// +// // 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. -// +// 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.) -// +// (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 +// understand how DNS and BIND works, however. There are sometimes // unobvious pitfalls. Setting up a secondary is comparably simpler. -// +// // NB: Don't blindly enable the examples below. :-) Use actual names -// and addresses instead. +// and addresses instead. /* zone "domain.com" { -- cgit v1.1