Prioritising Nameservers

[Barry Margolin]

In article <Pine.BSF.4.10.9907161638470.50341-100000 at tardis.wwiv.com>,
Berislav Todorovic  <BERI at etf.bg.ac.yu> wrote:
>In article <000401becf6b$01a69fe0$330b28c3 at ANDI.pool.net>,
>  <andi.twine at pool.net> wrote:
>> Does anyone know of a way to prioritise (like MX preferences) name
>> servers ?
>> ...
>> As dns2.nic.it is not running a completely up to date zone file - we
>> would like to prioritise them so dns2.nic.it is only used when
>> ns.pool.net is too busy.
>
>Well, with BIND 8.2.1 it is possible, though I've never tested it. The
>story goes something like this:
>
>options {
>   rrset-order {
>      class IN type NS name "mydomain.com" order fixed;
>      order cyclic;
>   };
>};
>
>As a result, NS records will always be returned in order in which they
>are defined in the zone file.

Since the order that the NS records are returned has little impact on the
order in which the servers are tried, I don't see how this could help.

-- 
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, 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.