problems with sortlist

Barry Margolin barmar at bbnplanet.com
Fri Jan 28 21:38:51 UTC 2000


In article <949072612.384411 at dibbs1.mpn.cp.philips.com>,
Frank van den Heuvel <Frank.vandenHeuvel at nl.origin-it.com> wrote:
>We are using BIND8.2.2-REL on BSDI 4.0.1 and we have a problem with
>sortlist.
>
>In our named.conf we have added the following under options:
>
>/* begin sortlist */
>        sortlist {
>                { localhost;
>                  { 172.16.30/24; };
>                };
>                { 172.16.30./24;
>                  { 172.16.30/24;
>                        {172.16.40/24 ; 172.16.50/24 ; 172.16.60/24 ; }; };
>                };
>        }; /* end sortlist */
>
>We also have a name that points to multiple addresses:
>172.16.30.12
>172.16.40.12
>172.16.50.12
>172.16.60.12
>
>We expect 172.16.30.12 as first in the response if we query from localhost
>or from a resolver with 172.16.30 address.
>But we get an IP address back following the round robin mechanism, so
>sortlist is not working as we expect it to work.
>
>Is there anybody who knows why it isn't working as we expect it to work ?

When you say "from a resolver", do you mean that you're querying a caching
server?  If so, *that* server will perform round-robin cycling of the
responses each time it answers from its cache.  Sortlist only affects the
order of responses sent by the authoritative server to the caching server.

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



More information about the bind-users mailing list