rndc.key

I am now running without chroot and relying on selinux for protection. I created a /etc/named.d/ directory for all my many includes in named.conf which I know I have to keep in /etc/ My rndc.key is in /etc/named.d/ and is an include in my named.conf. When I first started bind, it reported

How best to strip references to managed-keys.bind, bind.keys, rndc.key

Trying to get a clean set of logs. I'm guessing this has something to do with redefining 'view _default' and I'm having challenges figuring out how to do this. Someone point me to where _default is defined in the docs and I'll just remove appropriate references to the mentioned files. Thanks.

Re: rndc.key vs. rndc.conf

| Hi All: One more conf issue on bind 9.7.1-P2 | After running rndc-confgen and reloading BIND I?m getting this error: | WARNING: key file (/etc/namedb/rndc.key) exists, but using default | configuration file (/etc/namedb/rndc.conf) | rndc: connection to remote host closed | This may indicate

Re: rndc.key vs. rndc.conf

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/2/2010 5:08 PM, online-reg wrote: | Hi All: One more conf issue on bind 9.7.1-P2 | After running rndc-confgen and reloading BIND I?m getting this error: | WARNING: key file (/etc/namedb/rndc.key) exists, but using default | configuration file

Re: rndc.key vs. rndc.conf

On Sat, 2 Oct 2010, online-reg wrote: > Hi All: One more conf issue on bind 9.7.1-P2 >   > After running rndc-confgen and reloading BIND I?m getting this error: >   > WARNING: key file (/etc/namedb/rndc.key) exists, but using default > configuration file (/etc/namedb/rndc.conf)

rndc.key vs. rndc.conf

Hi All: One more conf issue on bind 9.7.1-P2 After running rndc-confgen and reloading BIND I’m getting this error: WARNING: key file (/etc/namedb/rndc.key) exists, but using default configuration file (/etc/namedb/rndc.conf) rndc: connection to remote host closed This may indicate that * the