Red Hat Bugzilla – Bug 165292
keys not accepted for secured updates (via GUI).
Last modified: 2007-11-30 17:11:11 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Description of problem: When adding a Named Key to secure DNS updates the keyword "key" is not added to the entry in named.conf. As a result named fails to start. If this keyword is manually added to named.conf then named starts (and works) fine, but after this you cannot edit the properties for the zone in system-config-bind (i.e. it seems to choke on the manually added keyword "key"). Version-Release number of selected component (if applicable): system-config-bind-4.0.0-20 How reproducible: Always Steps to Reproduce: 1.Add a Named Key to a zone in the BIND GUI. 2.Save and restart named. It will fail. 3.Manually edit named.conf to add the (missing) keyword "key" in front of the Name Key you are trying to add. 4.Restart named. It will now start fine. 5.Try to edit the zone in the BIND GUI now ... you cannot. Actual Results: See the notes above. Expected Results: See the notes above. Additional info: No.
This bug is now fixed with system-config-bind-4.0.0-26, available from: http://people.redhat.com/~jvdias/system-config-bind and shortly to be in FC-3 updates. Please try out the new version and let me know of any issues - thank you!