Running CentOS 5.2 with the following BIND update rpm, installed with "yum update" - bind-9.3.4-6.0.2.P1.el5_2.
Our master DNS has an rrset-order stanza with "order fixed" entries similar to the following:
rrset-order { class IN type A name "abc.foobar123.com" order fixed; class IN type A name "def.foobar123.com" order fixed; class IN type A name "ghi.foobar123.com" order fixed; [ stuff deleted ] }
When restarting BIND, I find LOTS of these entries in /var/log/messages:
rrset-order: order 'fixed' not fully implemented rrset-order: order 'fixed' not fully implemented rrset-order: order 'fixed' not fully implemented
According to this page, BIND can be compiled with the "enabled-fixed-rrset" option to support this. How to determine what switches were used to compile the BIND RPM I downloaded with "yum update?"
From http://www.isc.org/index.pl?/sw/bind/view/?release=9.5.0 :
2362. [cleanup] Make "rrset-order fixed" a compile-time option. settable by "./configure --enable-fixed-rrset". Disabled by default. [RT #17977]
Thanks,
=========Keith
According to this page, BIND can be compiled with the "enabled-fixed-rrset" option to support this. How to determine what switches were used to compile the BIND RPM I downloaded with "yum update?"
I was recently curious about this too. Is there an easier way than peering into the spec file? Thanks
-scott
Scott McClanahan wrote:
According to this page, BIND can be compiled with the "enabled-fixed-rrset" option to support this. How to determine what switches were used to compile the BIND RPM I downloaded with "yum update?"
I was recently curious about this too. Is there an easier way than peering into the spec file? Thanks
No, that is the only way I know.
The build log when we made it said:
./configure --build=i686-redhat-linux-gnu --host=i686-redhat-linux-gnu --target=i386-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --with-libtool --localstatedir=/var --enable-threads --enable-ipv6 --with-pic --with-openssl=/usr --enable-libbind 'CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -I/usr/kerberos/include
This is also in the log for "/lib/bind":
running /bin/sh './configure' --prefix=/usr '--build=i686-redhat-linux-gnu' '--host=i686-redhat-linux-gnu' '--target=i386-redhat-linux-gnu' '--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib' '--libexecdir=/usr/libexec' '--sharedstatedir=/usr/com' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-libtool' '--localstatedir=/var' '--enable-threads' '--enable-ipv6' '--with-pic' '--with-openssl=/usr' '--enable-libbind' 'CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -I/usr/kerberos/include ' 'CPPFLAGS= -I/usr/kerberos/include ' 'CXXFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables' 'FFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables' 'LDFLAGS= -L/usr/kerberos/lib ' 'build_alias=i686-redhat-linux-gnu' 'host_alias=i686-redhat-linux-gnu' 'target_alias=i386-redhat-linux-gnu' --cache-file=/dev/null --srcdir=.
But remember, we do not pick these switches, we build them like they are in RHEL.
--- On Tue, 8/12/08, Johnny Hughes johnny@centos.org wrote:
From: Johnny Hughes johnny@centos.org Subject: Re: [CentOS] bind-9.3.4-6.0.2.P1.el5_2 and rrset-order: order 'fixed'not fully implemented To: "CentOS mailing list" centos@centos.org Date: Tuesday, August 12, 2008, 5:34 PM Scott McClanahan wrote:
According to this page, BIND can be compiled with
the "enabled-fixed-rrset" option to support this. How to determine what switches were used to compile the BIND RPM I downloaded with "yum update?"
I was recently curious about this too. Is there an
easier way than
peering into the spec file? Thanks
No, that is the only way I know.
The build log when we made it said:
./configure --build=i686-redhat-linux-gnu --host=i686-redhat-linux-gnu --target=i386-redhat-linux-gnu --program-prefix= --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man --infodir=/usr/share/info --with-libtool --localstatedir=/var --enable-threads --enable-ipv6 --with-pic --with-openssl=/usr --enable-libbind 'CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -I/usr/kerberos/include
This is also in the log for "/lib/bind":
running /bin/sh './configure' --prefix=/usr '--build=i686-redhat-linux-gnu' '--host=i686-redhat-linux-gnu' '--target=i386-redhat-linux-gnu' '--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib' '--libexecdir=/usr/libexec' '--sharedstatedir=/usr/com' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-libtool' '--localstatedir=/var' '--enable-threads' '--enable-ipv6' '--with-pic' '--with-openssl=/usr' '--enable-libbind' 'CFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables -I/usr/kerberos/include ' 'CPPFLAGS= -I/usr/kerberos/include ' 'CXXFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables' 'FFLAGS=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 -march=i386 -mtune=generic -fasynchronous-unwind-tables' 'LDFLAGS= -L/usr/kerberos/lib ' 'build_alias=i686-redhat-linux-gnu' 'host_alias=i686-redhat-linux-gnu' 'target_alias=i386-redhat-linux-gnu' --cache-file=/dev/null --srcdir=.
But remember, we do not pick these switches, we build them like they are in RHEL.
Thanks for the info, Johnny --- I extracted the .src.rpm and edited the SPECS/bind.spec file, adding the --enable-fixed-rrset option to the list of options to "configure." After that, I ran rpmbuild, and saw "--enable-fixed-rrset" in my terminal's scrollback buffer.
Unfortunately that did not fix the problem. Do you have any other suggestions about other places in the SPECS/bind.spec file to put that option?
Interested in producing a compiled RPM with that option.
Thanks,
=======Keith
-
Johnny Hughes -
Keith Christian -
Scott McClanahan