Good morning,
We utilize a number of include files as part of our named.conf. I am
looking to see if there is a clever way to dump the entire named.conf
(or, even better, the entire RUNNING named.conf), which includes all the
include files.
I say running config, because sometimes you do an rndc
bin/tests/cfg_test --named /etc/named.conf
In message <1d8c9a4471119a40bd574f9d8d464ae304bd3...@xch60ykf.rim.net>, "Todd S
nyder" writes:
> Good morning,
>
> We utilize a number of include files as part of our named.conf. I am
> looking to see if there is a clever way to dump the entire
Hi I was trying to get the $generate directive to work like so
11 IN PTR 14.cool.com.
30 IN PTR 33.cool.com.
$GENERATE 11-30 ${3,0,d} PTR $.COOL.COM.
I've read the manual here
http://www.bind9.net/manual/bind/9.3.2/Bv9ARM.ch06.html#id2566761---
Syntax: $GENERATE range lhs [ttl] [clas
On Wed, 4 Mar 2009, Takahiro Masuda wrote:
>The tricky part is ${3,0,d} waas not working. I bumped into a site
> that stated $GENERATE range rhs type lhs
That is wrong.
> I then tried $GENERATE 11-30 $ PTR ${3,0,d}.COOL.COM. and this
> worked.
> Anybody here have the ability to update the man
In message <1e4079388e04544fa3ffa6a900d6fb65015d7...@exchange.vplsnet.net>, "Ta
kahiro Masuda" writes:
> Hi I was trying to get the $generate directive to work like so=20
>
> 11 IN PTR 14.cool.com.
>
>
>
> 30 IN PTR 33.cool.com.
>
> $GENERATE 11-30 ${3,0,d} PTR $.COOL.COM.
Which
Jeremy,
I don't think the definitions of "rhs" and "lhs" are at issue. What
apparently led the original poster to the wrong solution initially was
the verbiage in the manual stating "Any single *$* symbols within the
*lhs* side are replaced by the iterator value", which implies that "$"
replac
In message <49af42f8.9070...@chrysler.com>, Kevin Darcy writes:
> Jeremy,
> I don't think the definitions of "rhs" and "lhs" are at issue. What
> apparently led the original poster to the wrong solution initially was
> the verbiage in the manual stating "Any single *$* symbols within the
> *lhs
Mark Andrews wrote:
In message <49af42f8.9070...@chrysler.com>, Kevin Darcy writes:
Jeremy,
I don't think the definitions of "rhs" and "lhs" are at issue. What
apparently led the original poster to the wrong solution initially was
the verbiage in the manual stating "Any single *$* symbols w
I've built bind 9.6.0-P1 on NetBSD/i386 machines (versions 3.1, 4.0,
4.0.1 and 5.0_RC2) and discovered that nsupdate dumps core on the 4.x
ones.
The build process was just:
% sh -c './configure --disable-threads > configure.log 2>&1'
% sh -c 'make > make.log 2>&1'
% su
Password:
# sh -c 'make
Yes I guess I didn't understand it totally because in the example syntax is
shown as lhs defined at the beginning
$GENERATE range lhs [ttl] [class] type rhs [ comment ]
and when you read the explanation for lhs it shows the example ${-20,3,d}.
So I thought that ${-20,3,d} should be defined on the
10 matches
Mail list logo
