How to properly update chroot-bind

Lightner, Jeff JLightner at
Tue Jul 28 12:52:11 UTC 2015

Since the OP says he's not in Production yet I'd strongly advise moving on to CentOS 7 for multiple reasons.  I has a new base version of BIND and also has a 3.x kernel.

However, there is a learning curve because it also uses systemd rather than Sys V init.   The way bind-chroot runs is significantly different than it was on RHEL6 when you got to RHEL7.   (As noted CentOS versions are compiled from RHEL sources of the same versions.)

As noted previously on this list the version of  BIND you get with each major RHEL release (RHEL5, RHEL6, RHEL7) changes but the base version of BIND never gets updated to later BIND versions within each of these releases.  Instead RedHat backports security and some enhancements into the base they started with and add their own extended versioning.   This is true of CentOS because of its derivation.

There is someone on this list that does compile newer versions of BIND for RHEL so if you search the archive you can find newer versions than are shipped by RHEL/CentOS.   

Also CentOS does have extended repositories beyond those RHEL has so you may find something newer there.   

CentOS by the way is not "supported" so if you're using CentOS vs RHEL worrying about "supported" shouldn't be an issue for you.   (RHEL is "supported" if you pay for the subscriptions.)

-----Original Message-----
From: bind-users-bounces at [mailto:bind-users-bounces at] On Behalf Of Matus UHLAR - fantomas
Sent: Tuesday, July 28, 2015 7:58 AM
To: bind-users at
Subject: Re: How to properly update chroot-bind

>Am 28.07.2015 um 10:56 schrieb Matus UHLAR - fantomas:
>>>but you *never ever* should only update specific packages on a 
>>>RHEL/CentOS system because that is *not supported and tested* at all
>>No? What are dependencies for, then?
>>Or don't yum/RPM support them in the way debian does?
>>(that is why it's quite easy to have mixed Debian... we have machine 
>>with mix of debian 5,6,7 and even 8... not that It's good idea)

On 28.07.15 11:22, Reindl Harald wrote:
>CentOS is a RHEL clone except that there are no updates for older point 
>it was multiple times statet by the maintainers on the mailing list 
>that you have to apply *all* errata updates nothing else is supported
>it's not a matter of dependencies, it's just a matter of what 
>combinations of packages are tested for regressions and the fact that 
>there are no updates for RHEL without a good reason
>how does dependencies help when there was a critical bug fixed in 
>package A which may hit your updated version of package B because the 
>combination of that versions never was tested
>feel free to ignore that but you are at your own if things behave 
>unexpected when the developers say "just only use 'yum upgrade'"
>which applies also for minor releases, when CentOS 6.7 is out there 
>will be no single update for CentOS 6.6 packages and hence "yum 
>upgrade" brings you to CentOS 6.7 in a few weeks which is from that 
>moment on the only supported CentOS 6.x

yes, this is a good explanation, I believe for the OP too.

"not supported" can of course mean "working without problems", however I agree there's no point in only updating BIND itself.

Still, the OP can stick with provided BIND 9.8 that is in CentOS6, update to CentOS 7 or compile his own BIND version (and provide support for
Matus UHLAR - fantomas, uhlar at ;
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
REALITY.SYS corrupted. Press any key to reboot Universe.
Please visit to unsubscribe from this list

bind-users mailing list
bind-users at

More information about the bind-users mailing list