Sortlist...again

[Kevin Darcy]

Is the server in question authoritative for the zone containing the name
being queried? Is it the *only* server authoritative for that zone? If not,
then maybe the client is getting an answer from some other authoritative
server which doesn't have the same sortlist defined.


- Kevin

Anne LE DUIGOU wrote:

> Hi,
>
> I am new to this mailing-list, I've read this archive and seen a lot of
> questions related to the sortlist option but none seems to answer mine.
>
> I've configure sortlist statement:
>         sortlist {
>                         { 1.1.1.1;
>                                 { 2.2.2.69/32;};
>                         };
>                         { localhost;
>
>                                 {2.2.2.5/32; } ;
>                         };
>                         {1.1.2.1;
>                                 { 2.2.2.7/32;};
>                         };
>         };
>
> For localhost and 1.1.2.1 source the result is correct but not for the
> third one (I mean roun-robin apply and not sorting).
> You need aditionnal information:
> the server is BIND8.2.2P7
> localhost and 1.1.2.1 are SUN Netra with Solaris2.6
> 1.1.1.1 is a proprietary device with a resolver and implementing
> BIND4.9.7 for Cache-Only-Server, but TTL set to null in the record
> desactivate it (and so its round-robin function).
>
> I have checked with an analyser that this is the server that doesn't
> return the correct result (because it could be the client that reorder
> the answer)
>
> The only difference in the requests (between 1.1.2.1 and 1.1.1.1
> sources) are the source port (my device 1.1.1.1 is using the 53 port as
> source port) and the Recursion Desired bit, for my device it is not set.
>  Is it possible that one of these difference may cause problem to the
> server in order to perform the explicit sorting=3F
>
> Thank in advance for your answers,
> Anne