Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!sdd.hp.com!think.com!linus!agate!ucbvax!ISI.EDU!braden
From: braden@ISI.EDU
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re:  Pros and cons of secondary name servers off site
Message-ID: <9103071743.AA06347@braden.isi.edu>
Date: 7 Mar 91 17:43:30 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 29


	From namedroppers-RELAY@NIC.DDN.MIL Wed Mar  6 23:15:27 1991
	Date: Wed, 6 Mar 1991 12:55:19 -0800 (PST)
	From: wales@CS.UCLA.EDU
	To: namedroppers@nic.ddn.mil
	Subject: Pros and cons of secondary name servers off site

	What is the current policy/philosophy on having a copy of a domain's
	data stored on at least one "off-site" server (e.g., a secondary name
	server for UCLA data that is located somewhere other than UCLA)?

	When the domain system first came out, it was either a requirement or a
	strong recommendation that this should always be done.  However, when I
	looked through RFC 1123 (host software requirements) the other day, I
	was unable to find any comments on the issue of off-site name service.


Rich,

  The host requirements documents RFC-1122 and RFC-1123 were carefully
  limited to defining the requirements for host software, but not to
  specify how it is to be USED.  Thus, it generally does not give
  rules for operation or configuration of hosts, and therefore would
  not have anything to say about the way DNS components are configured.
  I would look to RFC-1032 and RFC-1033 for guidance on your question.  
  Regards,
  
     Bob Braden