Re: [cobalt-users] DNS - Basic Concepts and Instructions

[flash22@xxxxxxx]

On Sun, 6 May 2001, Rodolfo J. Paiz wrote:

> At 5/6/01 05:13 PM -0400, you wrote:
> >Looks like you have been busy :)
> 
> >A comment and an addition, I'd really drop the use of 'slave' entirely, it
> 
> Really? You sure? Let's debate this...
> 
> Both my Webmin and my bind-8.2.3 docs (everything I've read) uses master 
> zone and slave zone to refer to the relationship. Also, my named.conf file 
> uses the "type master" and "type slave" directives to describe a zone.
> 
> Let's try to figure out who's right on this one... I'm very confident in my 
> definition but that doesn't mean I'm *right*. To me, a caching-only 
> nameserver is a caching-only nameserver, and passing all requests to 
> another is "forwarding." No relation to being a slave that I know of.
> 
> Please argue.

 heh..

OK, i have this in mind...

http://www.intac.com/~cdp/cptd-faq/section4.html#slaves

Note that this is in reference to 'slave nameserver' not 'slave zone' ,
what you have for zones is exactly right, i am just wary of using the term
with 'nameserver' at all....because it refers to something totally
different than it does for a slave / secondary zone

aka master=authorative, slave=not authorative
   primary = has data for zone, secondary=gets data from primary

It's possible for example for a nameserver to be a 'master secondary
nameserver' for a zone...it's not a slave in any sense in this case

[confusing configration commands aside ;)]

gsh