Secondary nameserver not in record - possibly dumb question about this..

Peter Rose peter.rose1 at ntlworld.com
Thu Feb 22 22:00:18 UTC 2001


Thanks for that, I sort of thought that's what happened.

I have actually gone back to Chapeter 9 - but at the risk of sounding
incredibly thick  -

If, due to the fact that only bambam.swlink.net is shown as the
authoritative ns for usscreen.com, have I got this right that if bambam
is down and dino is queried, it will only tell the querying resolver to
go and ask bambam?
Would it not be possible that dino could answer from cache if it's
records for that domain have not expired - after all, it appears that
dino does have a zonefile for usscreen.com?

Sorry to be dense, I am but a seeker after truth:-)

Peter Rose
London UK
>There we go,
>
>When a resolver tries to resolve "mail.usscreen.com" it will
>traverse the DNS-tree down from "." unto ".com.".
>
>The ".com." nameserver tells the resolver, to get an authoritative answer
>for usscreen.com, it needs to ask dino or bambam. Lets assume bambam is
>dead, the resolver then asks dino. Dino says "authoritative" that the
>authoritative nameserver for usscreen.com is "bambam", which is dead.
>Badabing-Badaboom, usscreen.com is for this resolver. 
>
>You can find this at chapter 9 "Good Parenting" page 218. More examples
>there. Oh-yeah, "the guy" may want to upgrade dino and bambam.
>
>Regards,
>
>Roy Arends  
>Nominum.
>
>
>
>
>

"I don't like your fashion business mister" 
  - Leonard Cohen / First We Take Manhattan


More information about the bind-users mailing list