Hi,
I have multiple ip adresses for one server:
www.mydomain.com A 10.0.0.1
www.mydomain.com A 10.0.0.2
www.mydomain.com A 10.0.0.3
I need bind (I’m using 9.5.2-P1 on RedHat Linux Enterprise 5.4) to always return the first one (10.0.0.1) for everyone. So I check the Bind9 ARM and discovered the rrset-order option. It seems that using this option I can force bind to do what I want for that host.
The problem is that Bind9 does not support fixed ordering by default, unless I use –enable-fixed-rrset at compile time. When I add that to configure, I get several warnings:
# ./configure --enable-fixed-rrset --prefix=/usr/local --sysconfdir=/etc --localstatedir=/var
…
=== configuring in lib/bind (/root/named/bind-9.5.2-P1/lib/bind)
configure: running /bin/sh ./configure '--prefix=/usr/local' '--enable-fixed-rrset' '--sysconfdir=/etc' '--localstatedir=/var' --cache-file=/dev/null --srcdir=.
configure: WARNING: Unrecognized options: --enable-fixed-rrset
…
configure: creating ./config.status
…
configure: WARNING: Unrecognized options: --enable-fixed-rrset
They are just warning, so I ignored them and tried the rrset-order option like in the ARM example in my named.conf:
rrset-order {
class IN type A name "www.mydomain.com" order fixed;
order cyclic;
};
If I try to start bind I get this error:
Error in named configuration:
/var/named/conf/options:20: unknown option 'rrset-order'
If I remove the option there’s no error starting named.
What am I doing wrong???
Thanks,
Denis Laventure
It may not do everything that you are expecting, however. Only the
authoritative server will be required to pass the ordering of your RRSET
out as you specify. All intervening caching servers will re-order the
records as they see fit. The ordering of the RRSET is not guaranteed by
the RFCs so if what you are trying to do works, you will be lucky, and
the behavior may change at any time.
> configure: WARNING: Unrecognized options: --enable-fixed-rrset
> They are just warning, so I ignored them and tried the rrset-order
> option like in the ARM example in my named.conf:
My guess is that you may not have done a "make clean" after you
re-configured. If you just "./configure <blah> && make", not all of the
dependencies are re-compiled...
On 19.02.10 11:16, Alan Clegg wrote:
> It may not do everything that you are expecting, however. Only the
> authoritative server will be required to pass the ordering of your RRSET
> out as you specify. All intervening caching servers will re-order the
> records as they see fit. The ordering of the RRSET is not guaranteed by
> the RFCs so if what you are trying to do works, you will be lucky, and
> the behavior may change at any time.
there's sortlist option that should do what he wants, however it depends on
source IP, not the destination RRset.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Support bacteria - they're the only culture some people have.