NS record question
bobvance at alumni.caltech.edu
Mon Mar 26 20:05:40 UTC 2001
Oh, thanks, Roy.
Now, I'm really confused :)
>The master does not send NOTIFY to servers specified by zone-cut NS
Well, what NS records *does* it use??
(Of course, I believe that in our context -- same server -- all the NS
records appear together for the child zone, regardless of where they
>The question was what the problems would be when zone-cut NS
>records were removed from the zone, when the cutted zone (child zone,
>delegated zone) resides on the same server.
And I think that there is *no* problem, as my other post mentioned.
Tks | <mailto:BVance at sbm.com>
BV | <mailto:BobVance at alumni.caltech.edu>
Sr. Technical Consultant, SBM, A Gates/Arrow Co.
Vox 770-623-3430 11455 Lakefield Dr.
Fax 770-623-3429 Duluth, GA 30097-1511
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Roy Arends
Sent: Monday, March 26, 2001 3:22 PM
To: Bob Vance
Cc: bind-users at isc.org
Subject: RE: NS record question
On Mon, 26 Mar 2001, Bob Vance wrote:
> >There is no NOTIFY issue. Notifies get sent to slave servers, not to
> >zones. This discussion was about omitting NS records for delegation
> >child is hosted from the same server. Not a discussion about the NS
> >residing and a zones apex.
> My point was that if you had a secondary server for the sub-zone,
> would otherwise work correctly (even without the NS records) for
> requests to that sub-zone, but there were no NS records, then the
> secondary would not get NOTIFYed when changes were made on the
> At least, I thought that was correct -- that the primary uses the NS
> records to decide whom to NOTIFY.
> Besides, you were the one that brought up secondary servers :)
Yes, but the master sends NOTIFY to the NS records at the zone top. You
are right when it comes to omitting them, the slaves would not get
The master does not send NOTIFY to servers specified by zone-cut NS
records. The question was what the problems would be when zone-cut NS
records were removed from the zone, when the cutted zone (child zone,
delegated zone) resides on the same server.
Apologies if I was too direct.
More information about the bind-users