TLD nameservers that also cache?

Jim Reid jim at
Thu Jul 6 18:47:10 UTC 2000

>>>>> "Brad" == Brad Knowles <blk at> writes:

    Brad> 	The only other solution I can think of is to change
    Brad> the behaviour of caching/recursive nameservers.  Instead of
    Brad> having it go all the way to the root nameservers and ask the
    Brad> question "", and following the referral,
    Brad> it should assume that the higher level nameservers are
    Brad> non-caching and reduce the query appropriately.  In this
    Brad> case, it should ask them "be/IN/NS", follow the referrals to
    Brad> the nameservers for ".be", then ask "" to one
    Brad> or more of them, and then and only then should it finally
    Brad> ask the question "".

Aside from the problems of updating RFC103[45] and getting the new
code written and deployed, I don't think this would work. What about
non-terminal names that don't have a zone cut? Suppose
existed but there was no zone? And what about intranets that
have their own internal roots and could be playing by different rules
about where Nth-Level domain servers handle recursive queries? Maybe
they don't have any top-level zones at all and delegate,, etc directly off their own root zone?

More information about the bind-workers mailing list