BIND failure methods (NS)

[Barry Margolin]

In article <38FD0511.66D27686 at mindspring.com>,
ddd  <mjy78 at mindspring.com> wrote:
>For one I may think that the querying server really only needs one NS glue
>record in order to find that given domain, then it queries that domain srever
>for whatever records it needs. If it can't contact one NS/A given by parent,
>then it could contact parent again for the next one...?  That's good though.
>So what the parent answers with is _all_ NS records and associated glue
>records it has for that queried domain ?

Correct.

>The Querying party then tries to contact each, and all nameservers will at
>least fail over to the next one in the list, and/or use any available with the
>least RTT ?

Correct.

>So it seems that the good news is that if we have 3 NS machines listed at our
>parent, and we want to change the address of one of them, the other 2 will
>answer all queries ?

Correct.

>What about if a server has ALREADY received 3 NS & A records from our parent,
>and those TTL's are 24hrs, if all 3 become unavailable during the 24 hrs, will
>the Querying party re-query the parent BEFORE the TTL has expired ?

No, sorry.

-- 
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.