Bug 141818
Summary: | BIND GUI bugs SOA formatting | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Nick Fisher <redhat> |
Component: | redhat-config-bind | Assignee: | Radek Vokál <rvokal> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | ovasik |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-02-18 09:16:40 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: | |||
Bug Blocks: | 189875 |
Description
Nick Fisher
2004-12-03 21:55:53 UTC
Yes, there are alot of problems with the current system-config-bind . I am just completing a complete rewrite which should be done this week, and which does not have this problem. I'll update this bug when it is released. Well I can only assume that the updated packages I got today included the new tool. Totaly against the 'rpm way' they blew away my named.conf and replaced it with a new config file. It's also still not at all clear how or when you are supposed to use named.custom. """ # Any changes not currently supported by redhat-config-bind should be put # in this file. """ All well and good but nowhere does it say what isn't currently supported by redhat-config-bind. As before, all I can do is not use the GUI in fear that it will mess things up. Oh and keep a backup copy of the named.conf incase any of hte new RPMs eat it again. A version which fixes these problems, redhat-config-bind-4.0.0-16, is now submitted to RHEL-3 and should be in RHEL-3-U6 . Meanwhile, it can be downloaded from: http://people.redhat.com/~jvdias/redhat-config-bind It definitely writes correct SOA records and supports all named.conf constructs and so no longer requires named.custom . Please try out this version and let me know of any issues - thank you. |