sortlist question
Kevin Darcy
kcd at daimlerchrysler.com
Tue Dec 12 22:32:32 UTC 2000
Offhand, it seems like your sortlist should do what you want. But, to be
perfectly honest, although I have used sortlists quite extensively, I've
never used more than a single "sort" element (i.e. where each element
gets assigned a distance, etc.). Perhaps you could try simplifying the
sortlist and see where it breaks. At the very least, it may help you
diagnose the problem. You may even discover that a simpler sortlist
meets your requirements.
- Kevin
Thomas Duterme wrote:
> Hi all,
>
> I'm trying to configure my internal split properly by using
> a sortlist.
>
> let's say I have multiple names like the following (ie 2 or
> more A records per name):
> madeforchina.com IN A 211.101.228.18
> IN A 192.168.8.3
>
> Here's what I want to do: I have 192.168.8/24 as my LAN.
> I want 192.168.8.0/25 to ALWAYS get back one version (the
> 192 network) of a roundrobin record and I want
> 192.168.8.128/25 to get the other...again always first. (the
> 211 network) I haven't thought of a way for the nameserver
> to only send back one version of the roundrobin, but I
> figure that using the sortlist below, should always give
> back the proper answer.
>
> Here's what I've done:
>
> sortlist {
> { localhost;
> { 192.168.8/24;
> 172.18.1/24;
> { 211.99.193.0/27;
> 211.99.175.64/27; }; }; };
> { 192.168.8.0/25;
> { 192.168.8/24;
> 172.18.1/24;
> { 211.99.193.0/27;
> 211.99.175.64/27; }; }; };
> { 192.168.8.128/25;
> { 211.99.193.0/27;
> 211.99.175.64/27;
> { 192.168.8/24; 172.18.1/24; }; };
> };
> };
>
> Why is it that I've got some clients on the 192.168.8.128/25
> portion of the network which is picking up the 192 network
> first when it should be getting the 211 network? Am I
> missing anything?
More information about the bind-users
mailing list