Bug 203070
Summary: | rndc.conf change breaks working bind config | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Martin Stransky <stransky> | ||||
Component: | bind | Assignee: | Martin Stransky <stransky> | ||||
Status: | CLOSED ERRATA | QA Contact: | Ben Levenson <benl> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4.4 | CC: | Colin.Simpson, me, milan.kerslager, nalin, redbugme3210, suzuki-t, ubeck | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | RHBA-2006-0711 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2006-11-03 16:15:46 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Bug Depends On: | 202012 | ||||||
Bug Blocks: | |||||||
Attachments: |
|
Description
Martin Stransky
2006-08-18 09:39:55 UTC
Created attachment 134429 [details]
proposed patch
bind-9.2.1-key.patch really fixes this problem, unfortunately it isn't included in 4.4 So does that mean there will be an update to fix this soon?? Essentially this has broken all of the previously working bind configs for el3 and el4. Yes, I know once you understand what happened, it is easy to fix but that is not the point. It seems that the real cause is that the key in chroot /var/named/chroot/etc/rndc.key differ from one provided in /etc/rndc.conf. This may be caused by a bug in pre or post scripts. They are really ugly and very complicated. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. Fixed srpm packages (for RHEL3 and RHEL4) are here: http://people.redhat.com/stransky/bind/ An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2006-0711.html The RPM package for the errata does not seem to be available. Can someone push this to RHN? Thanks. Shawn. Nevermind it's under 'Fastrack' For those who has broken config: copy secret from /etc/rndc.conf (this could be a symlink to /var/named/chroot/etc/rndc.key if you have bind-chroot installed) to the secret in /etc/rndc.conf. For those who has broken config: copy secret from /etc/rndc.conf (this could be a symlink to /var/named/chroot/etc/rndc.key if you have bind-chroot installed) to the secret in /etc/rndc.key (TYPO FIX). bind-9.2.4-20.EL4 worked. But why was this fix put into the Fastrack channel? Shouldn't it be a normal bug fix update? This involves a relatively severe problem for BIND administrators, especially if dynamic and static updates are used together: when terminating named with `service named stop', /usr/sbin/rndc doesn't work and failsafing killproc is actually used in the /etc/init.d/named script. So .jnl dynamic update caches won't be flushed and zone files are still obsolete after the termination. Will be fixed in bind-9.2.4-24.EL4 and it's on the way. Hello Uwe, this will be fixed in bind-9.2.4-24.EL4 and it's fixed in an errata on RHN https://rhn.redhat.com/network/software/packages/details.pxt?pid=382408 Hence closing this issue. Kind regards, Steffen Internal Status set to 'Resolved' Status set to: Closed by Client Resolution set to: 'RHEL 4.5' Ticket type set to: 'Problem' This event sent from IssueTracker by smann issue 100769 |