From RHEL to CentOS BIND 9
isplist at logicore.net
isplist at logicore.net
Wed Dec 5 21:54:55 UTC 2007
Well, then I'm extra confused.
I uninstalled both bind, bind-chroot and bind-utils as well.
I then re-installed bind-chroot and bind-utils, copied my files over, changed
the permissions to named.named and it worked.
I can't tell you why I'm having so many problems but if I am, I'm guessing I
can't be the only one. Makes me wonder how many just plain quit and you never
hear/know about it.
Mike
On Wed, 5 Dec 2007 15:24:52 -0600, Baird, Josh wrote:
> bind-chroot is a supplement package to bind. You need them both, "bind"
>
> is a dependency of "bind-chroot."
>
> I'm not sure why you are having so many problems.. I have deployed a lot
> of bind-chroot'd installations without any problems whatsoever using
> "yum install bind-chroot."
>
> Once again, this is not in the scope of this list, so I will call it
> quits here.
>
> Josh
>
> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> Behalf Of isplist at logicore.net
> Sent: Wednesday, December 05, 2007 3:18 PM
> To: bind-users
> Subject: Re: From RHEL to CentOS BIND 9
>
>> The keys used for rndc (in the named.conf and rndc.key) should not be
>> shared between multiple nameservers. If you wish to administer
> multiple
>
> Got it. That's what I figured since I did have transfers working before
> all of
> this went haywire but could not recall. I'll remember this.
>
> Much appreciated.
>
>
> At this point, I'm going to uninstall and start over again. It looks
> like bind
> and bind-chroot get installed together and mess things up. It turns out,
> this
> is why I have mixed non and chrooted configurations as someone pointed
> out.
>
> Hope someone who has anything to do with installers is reading this. I
> am
> happy to reiterate if you'd like more information.
>
> Mike
More information about the bind-users
mailing list