Why is stealth secondary queried for address of primary?

[Barry Margolin]

In article <394a64d9$0$24109 at wodc7nh6.news.uu.net>,
Super-User <root at tsi-telsys.com> wrote:
>In article <200006152123.HAA04977 at bsdi.dv.isc.org>,
>	Mark.Andrews at nominum.com writes:
>> 
>>> At 07:12 PM 06/15/00 +1000, Mark.Andrews at nominum.com wrote:
>>> >
>>> >	Well nameservers send out the current set of nameservers for the
>>> >	zone as found in the zone.  If you want a server to be a stealh
>>> >	server don't=A0list it in the zone or the parent zone.
>>> 
>>> Yes, I understand that.  I used the wrong term -- I said stealth only
>>> because it it's not listed in the root servers.  I just haven't updated my
>>> domain record yet.
>
>Could you explain that? For a stealth server, is it sufficient to put a
>"notify no" in each zone stanza?  what does "don't=A0list it in the zone"
>mean?

A stealth server is a server that isn't mentioned in any NS records, so
that no one knows to query it.  Typically it's a server local to the
network that's using the domain, and listed in the client machines'
resolver settings (e.g. /etc/resolv.conf).  "Don't list in the zone" means
not to put:

thisdomain.com.  IN NS  stealthNS.thisdomain.com.

in the zone file.

You probably want to put:

	also-notify { address of stealthNS; };

in the zone stanza, since by default only the servers listed in NS records
are notified.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.