Runtime disable RRL

Is there a runtime switch or config option to disable RRL. The bind 9.9.5-S1 by default included the RRL enable but we would like to run test with and without the RRL active. Rick. smime.p7s Description: S/MIME cryptographic signature ___ Please

RE: Runtime disable RRL

Thanks. We'll try this, otherwise I guess I'll just build a separate binary with RRL disabled. -Original Message- From: Jeremy C. Reed [mailto:jr...@isc.org] Sent: Tuesday, August 19, 2014 11:15 AM To: Olsen, Richard William (Rick) CTR DISA PEO-MA (US) Cc: bind-users@lists.isc.org

RE: Cross compile bind failing, vis3 ???

the configure script to have cross_compile=yes, it still responds with no during the configuration. -Original Message- From: Mark Andrews [mailto:ma...@isc.org] Sent: Monday, April 28, 2014 12:05 PM To: Olsen, Richard William (Rick) CTR DISA PEO-MA (US) Cc: bind-users@lists.isc.org Subject: Re

Cross compile bind failing, vis3 ???

We have a remote site that we are providing a bind package for. They want a targeted build and sent us the compile options as -xtarget=T3 -xarch=sparcvis3 -xchip=ultraT3 -xcache=8/16/4:6144/64/24 The build system is using Sun Studio 12.3 cc on T5140 (UtltraSPARC-T2+ hardware running Solaris

Bind 9.9.5-S1 Cross Compile help

We are trying build out bind for a remote site. When I use the prefix option so that I can put it all where I can package it, it hardcodes the prefix into the named binary for several items. How do I get around that. The hardcoded entries are for rndc.key, name.conf, session.key, named.pid,

FW: Bind 9.9.5-S1 Cross Compile help

2014, at 17:57, Olsen, Richard William (Rick) CTR DISA PEO-MA (US) richard.w.olsen@mail.mil wrote: We are trying build out bind for a remote site. When I use the prefix option so that I can put it all where I can package it, it hardcodes the prefix into the named binary for several items

Trouble building bind with Openssl support

We have been trying to build bind using with-openssl=PATH and not have it require the full openssl install on the destination system. We had this setup and running when we were building on solaris 9 using bind-9.9.2 up through bind-9.9.4-P2. Now we are building on a Solaris 10 system (remote

Bind-9.9.4-S3 RRL

Reading different pages I have seen that you needed to use --enable-rrl as a configuration option but it is not in the S3 release. So is it the default or not available in the S3. The public release does have a rrl option. Rick. smime.p7s Description: S/MIME cryptographic signature