I guess I wasn't overly clear in my question, but I got some good answers
anyway. The question probably should have been phrased:
I have my machine set up a a primary name server for my domain, and need to
add the capability to be a secondary server for someone else's domain.
But I didn't. Anyway, the correct answer is:
Add a line like the following to your named.boot file:
secondary <Domainname> <Primary> <File>
and restart named. That simple.
Anyway, much thanks to:
Eckhard.Rueggeberg@ts.go.dlr.de (Eckhard Rueggeberg)
bern@penthesilea.Uni-Trier.DE (Jochen Bern) - Who provided great details!
Larry Chin <Larry_Chin@ca.cch.com>
rwh@atmos.albany.edu (Ronald W. Henderson)
Craig.Hunt@nist.gov (Craig Hunt)
kumeda@tds.com (Andy Kumeda)
Thanks again,
Bob
Replies follow
->From sun-managers-relay@ra.mcs.anl.gov Tue Jun 14 20:56 EDT 1994
->Date: Tue, 14 Jun 1994 17:04:39 +0500
->From: bownes@lucas.emi.com (R.M. Bownes III)
->To: sun-managers@eecs.nwu.edu
->Subject: Setting up a secondary name server
->
->Subject: Setting up a secondary name server
->Content-Length: 316
->
->
->
-> Help!
-> We need to set up our primary name server as a secondary
->server for some of the folks work work with. They have a separate name
->and IP domain. I have no clue whatinthehell needs to be done, the two
->O'Reilly books I have are of little help, and the Sun 2.3 docs are of
->even less help.
->
->
-> Thanks!
-> Bob
->
->
->From Eckhard.Rueggeberg@ts.go.dlr.de Wed Jun 15 02:18 EDT 1994
->Date: Wed, 15 Jun 1994 08:15:10 --100
->From: Eckhard.Rueggeberg@ts.go.dlr.de (Eckhard Rueggeberg)
->To: bownes@lucas.emi.com
->Subject: Re: Setting up a secondary name server
->
->You need only one line in your named.boot file, e.g. after the
->line with primary definition, of the following form :
->
-> secondary <domainname> <internet-nr-of-server> <filename>
->
->Our named.boot look like
->
-> directory /etc/named
->
-> cache . named.ca
->
-> primary ts.go.dlr.de named.local
-> primary 66.247.129.IN-ADDR.ARPA named.rev.66
-> secondary go.dlr.de 129.247.64.1 dlr.zone
->
->Hope this helps
->
->Eckhard R|ggeberg
->eckhard@ts.go.dlr.de
->
->From bern@penthesilea.Uni-Trier.DE Wed Jun 15 06:23 EDT 1994
->Date: Wed, 15 Jun 94 12:19:32 +0200
->From: bern@penthesilea.Uni-Trier.DE (Jochen Bern)
->To: bownes@lucas.emi.com
->Subject: Re: Setting up a secondary name server
->
->Well OK, I just set up a secondary from Scratch, so I have the Info
->handy, er, brainy ...
->
->First: What named are you running, the SunOS one or the PD BIND Package
->one? (If you don't know, run "strings" on it, the first Line reads, e.g.,
->
-> @(#)named 4.9 Wed Jun 8 23:32:30 MET DST 1994 Bern@kleopatra:/src/named.4.9.930
-> ^^^^^^^^^^^^^^
->
->for the BIND named and
->
-> @(#)db_dump.c 1.10 89/02/14 SMI
-> ^^^
->
->for the SunOS named.)
->
->In both Cases, what you're looking for should be in a File which is given to
->named as a Command Parameter, or /etc/named.boot if there is no Parameter.
->
->Supposed that your Setup for the primary Zone is OK, all you need is to
->a) tell your named to be a Secondary of the other Zone,
->b) give it a Kick so that it reads the new Info.
->
->Ad a) In /etc/named.boot (or wherever the Param points to), right after
-> your "primary" Lines, add a Line:
-> secondary <Domainname> <Primary> [ <Secondary> ... ] <File>
-> I.e., be a Secondary for the named Domain, get your Data from the
-> Primary in normal Operation, from the named Secondaries if need be,
-> and save the Information in the named File for faster Startup.
-> (The Directory of the File is as given by the "directory" Option,
-> Default /etc.) Give all Hosts as *IP Numbers*, not Names!
-> Supposed that their Network is 135.123.0.0, you add a second Line:
-> secondary 123.135.IN-ADDR.ARPA <Primary> [ <Secondary> ... ] <File>
-> for the reverse Lookups. Note that the Number of Numbers to use
-> depends on the Type of Network (A, B, C) they have.
-> If the Primary runs BIND named, note that "Zone Transfers" (that's
-> how a Secondary gets the Info from the Primary) will be denied by
-> the Primary unless the requesting Host is in a Network given in the
-> "xfrnets" Line of /etc/named.boot.
->Ad b) A properly configured named should write his PId into a File called
-> /etc/named.pid, so telling it to reread the Config is achieved with
-> "kill -HUP `cat /etc/named.pid`". If not, find out the PId with
-> "ps -ax | grep named" and kill -HUP it then. To verify that everything
-> is OK, do a kill -TERM, which should cause it to write all Data to
-> the Files given in /etc/named.boot (but wait 'til it has successfully
-> xfered the Data from the Primary :-).
->
->Note that if the Domain was a Subdomain of yours (Name-wise), there would
->have been a little more to do.
->
->Regards,
-> J. Bern
->--
->__/\_____________________________________________ ___________________________
-> / \ \ / /\
->/ J. \ EMail: bern@[TI.]Uni-Trier.DE / ham: DD0KZ X More Infos on me from / \
->\Bern/ X.400: <---- temporarily disabled ----> / \ the X.500 Directory; \ /
-> \ / P. O. Box 1203, 54202 Trier, Germany / \ Pub Keys via finger \/
->__\/___________________________________________/ EOF \_________________________
->
->From Larry_Chin@ca.cch.com Wed Jun 15 06:25 EDT 1994
->Date: Wed, 15 Jun 1994 06:24:17 -0400
->From: Larry Chin <Larry_Chin@ca.cch.com>
->To: bownes@lucas.emi.com
->Subject: Re: Setting up a secondary name server
->
-
->
->Add the following lines to YOUR named.boot.
->
->secondary <their domain> <their primary DNS server' IP address> <name of file to store info in
->
->
->I believe that is all that you have to do. Check pages 79-81 of the O'Reilly
->DNS and Bind book.
->
->If I haven't made this clear, drop me a line.
->
->
->Wed Jun 15 06:24:05 EDT 1994
->===========================================================================
->Larry Chin {larry@cchtor.ca.cch.com} CCH Canadian Ltd.
->System Administrator 6 Garamond Court
->Research and Development North York, Ontario.
->(416) 441-4001 ext. 349 M3C 1Z5
->===========================================================================
->
->Gerrold's Laws of Infernal Dynamics:
-> 1. An object in motion will always be headed in the wrong
-> direction.
-> 2. An object at rest will always be in the wrong place.
-> 3. The energy required to change either one of these states
-> will always be more than you wish to expend, but never so
-> much as to make the task totally impossible.
->
->From rwh@atmos.albany.edu Wed Jun 15 08:32 EDT 1994
->Date: Wed, 15 Jun 1994 12:29:18 +0000
->From: rwh@atmos.albany.edu (Ronald W. Henderson)
->To: bownes@lucas.emi.com
->Subject: Re: Setting up a secondary name server
->
->
->Bob:
->
->In your named.boot file add a secondary statement for the new IP name and
->domain. The primary server for this domain must have glue records (NS records)
->that point to lucas as the secondary server for this domain.
->
-> ________ __ __ __ __
-> /\_\_\_\_\ /\_\ /\_\ /\_\ /\_\
-> /\/_/_/_/_/ /\/_/ /\/_/ /\/_/ /\/_/ Ronald W. Henderson
-> /\/_/__\/_/ /\/_/ __ /\/_/ /\/_/___/\/_/ SUNY-Albany
-> /\/_/_/_/_/ /\/_/ /\_\ /\/_/ /\/_/_/_/_/_/ (518) 442-4571 Phone
-> /\/_/ \/_/ /\/_/_/\/_/_/\/_/ /\/_/ /\/_/ (518) 442-5825 Fax
-> \/_/ \/_/ \/_/_/_/_/_/_/_/ \/_/ \/_/ rwh@atmos.albany.edu
-> --------------------------------------------------------------------
->
->
->
->From @PUCC.PRINCETON.EDU,@DUVM.OCS.DREXEL.EDU:MEYSTMA@DUVM.OCS.DREXEL.EDU Wed Jun 15 11:58 EDT 1994
->Date: Tue, 14 Jun 94 20:44:08 EDT
->From: "Michael (M.A.) Meystel" <MEYSTMA%DUVM.BITNET@pucc.Princeton.EDU>
->Subject: Re: Setting up a secondary name server
->To: "R.M. Bownes III" <bownes@lucas.emi.com>
->
->Hello,
->
->I would appreciate seeing any responses you receive to your question.
->We have a similar situation developing, and also do not know what to do.
->Thank you in advance.
->
->Michael A. Meystel
->Systems & Network Administrator
->College of Engineering
->Drexel University, Philadelphia, PA USA
->+ 1 215 895 5807 / fax + 1 215 895 4929 / meystel@impact.drexel.edu
->
->From Craig.Hunt@nist.gov Wed Jun 15 14:59 EDT 1994
->Date: Wed, 15 Jun 94 15:00:18 EDT
->From: Craig.Hunt@nist.gov (Craig Hunt)
->To: bownes@ftp.emi.com
->Subject: Re: Setting up a secondary name server
->
->
->Bob,
->
->Look on page 176 of the O'Reilly TCP/IP Network Administration book.
->All you need to do is add secondary statements to your named.boot file
->for the domains for which you want to be a secondary. Assume that the
->domain run by the other people is "other.com", that the reverse domain
->they run is "99.12.199.in-addr.arpa", and that the address of their
->primary server is 199.12.99.1. The following two lines added to
->named.boot would be all that was necessary to provide them secondary
->name service:
->
->secondary other.com 199.12.99.1 other.com.hosts
->secondary 99.12.199.in-addr.arap 199.12.99.1 other.com.rev
->
->--Craig
->
->From kumeda@tds.com Thu Jun 16 01:08 EDT 1994
->From: kumeda@tds.com (Andy Kumeda)
->Subject: Re: Setting up a secondary name server
->To: bownes@lucas.emi.com
->Date: Wed, 15 Jun 1994 22:05:05 -0700 (PDT)
->X-Phone: (310) 348-6327
->Mime-Version: 1.0
->Content-Transfer-Encoding: 7bit
->
->R.M. Bownes III wrote:
->
->#
-># Subject: Setting up a secondary name server
-># Content-Length: 316
->#
->#
->#
-># Help!
-># We need to set up our primary name server as a secondary
-># server for some of the folks work work with. They have a separate name
-># and IP domain. I have no clue whatinthehell needs to be done, the two
-># O'Reilly books I have are of little help, and the Sun 2.3 docs are of
-># even less help.
->
->hmmm.... I have to assume that neither of the O'Reilly's you have are
->the DNS/BIND book, because that will definitely tell you how. I don't
->have the book with me now, but there is a 'cookbook' method described in
->the DNS book on how to setup a secondary. I followed it, and didn't
->have any problems.
->
->#
->#
-># Thanks!
-># Bob
->#
->#
->
->--
->Andy Kumeda Trident Data Systems [ PGP Key
->E-mail: kumeda@tds.com 5933 West Century Blvd Available
->Voice: (310) 348-6327 Suite 700 Upon
->FAX: (310) 649-5437 Los Angeles, CA 90045 Request ]
->
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:04 CDT