rrset-order in 9.3

[Scott Moseman]

I'm not sure that my rrset-order is actually working in 9.4.

# named -v
BIND 9.4.1-P1

# cat named.conf | grep rrset
rrset-order { name "sub.domain.com" order fixed; };

# cat sub.domain.com | grep A | head -3 | tail -2
as A 10.1.157.3
 A 10.1.158.3

However, doing 'nslookup as.sub.domain.com' still is random.
Am I doing something wrong?  Does anyone use rrset-order?

Thanks,
Scott



On 3/22/07, Kal Feher <kal.feher at melbourneit.com.au> wrote:
>
> You may be interested to note that included with the release notes
> for BIND 9.4 is the line:
>
> Implement "rrset-order fixed"
>
> "Cyclic" and "random" are not present in the release notes. Since
> cyclic is standard, the only remaining uncertainty is whether "random"
> has been implemented.
>
>
> On 22/3/07 3:34 AM, "Scott Moseman" <scmoseman at gmail.com> wrote:
>
> > I will recall this question.  Using 'nslookup' it does not work, but
> > using 'dig' it does work.  I'm going to assume that 'nslookup' was not
> > doing the appropriate query type or something.  In any event, we have
> > this working in our 9.3 environment now.
> >
> > Thanks,
> > Scott
> >
> >
> > On 3/21/07, Scott Moseman <scmoseman at gmail.com> wrote:
> >>
> >> The 9.x admin guides reference the rrset-order option.  But they also
> >> claim its not supported in 9.x releases (yet).  We have been tinkering
> >> with this option in our 9.2 and 9.3 environments and they are not
> >> working.  Is it *true* its not supported in 9.x releases?  If so, why
> >> does it remain in the documentation?  If it's not supported, what's
> >> the current procedure for stopping round robin results in favor of
> >> ordered results?
> >>
> >> Thanks,
> >> Scott
> >>
>
> --
> Kal Feher
> Team Leader
> Network Services and Production Support
> Melbourne IT Ltd
> Level 2, 120 King Street
> Melbourne Victoria 3000
> AUSTRALIA
> Ph:    + 61 3 8624 2326
> Mob:   + 61 400 072 569
> Website:   www.MelbourneIT.com.au
>