bind9 questions

[Timothy.Moseley at hurlburt.af.mil]

Okay, now we are getting somewhere, if all I need to do is add a key
statement to my named.conf file that is empty then I will give that a try,
the manuals do not state that you can use a null value in the key statement.
I do not have to worry about anybody on my network running rndc, that is
what the OSI and FBI are for. I will try the null thing and let you know if
it works.

NOPE.
So I guess w/out the key bind9 does not work.

> >-----Original Message-----
> >From: Jim Reid [mailto:jim at rfc1035.com]
> >Sent: Thursday, March 01, 2001 8:38 AM
> >To: Timothy.Moseley at hurlburt.af.mil
> >Cc: bind-users at isc.org
> >Subject: Re: bind9 questions 
> >
> >
> >>>>>> "Timothy" == Timothy Moseley 
> ><Timothy.Moseley at hurlburt.af.mil> writes:
> >
> >    Timothy> As I said QIP (the master) does not support keys.
> >
> >You'll have to take that up with the vendor. Why should this matter
> >anyway? You're configuring the slave server yourself, so what's
> >preventing you from adding a key{} statement to its named.conf? Or
> >are you relying on QIP to generate that file? Even so, it should be
> >trivial to fix up that QIP-generated file so that the missing key{}
> >statements and whatever get added correctly.
> >
> >    Timothy> That is why I tried the rndc.conf w/out the key 
> >statement 
> >    Timothy> first, I am wanting to know how I can configure 
> >the .conf 
> >    Timothy> file w/out it and still get rndc to work.
> >
> >You can't. Well I suppose you probably could have the null 
> >string as a
> >key, but this would still need a key{} statement defined in 
> >named.conf
> >and rndc.conf. And with an empty key, your name server could be
> >controlled by anyone running rndc on your network. This is probably
> >not a good thing.
> >