Hide Forgot
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: There are two problems I think I have found with the BIND GUI. 1) When creating a new zone using the GUI, the tool puts the 'primary nameserver' as the first feild in the SOA. This should be the domain name or @. The primary namserver should be the fourth feild. The primary nameserver feild is *always* set to localhost by the GUI. 2) Apparently named.custom is for putting unsupported config vars into. However it's not included in the main named.conf. How are the directives in that file ever going to be used? I'm guessing that the default named.conf should also have an 'include' line that includes named.custom. Having said that, in the current deployment, including the custom file would lead to two options directives and two "." zones. I'm having trouble seeing how named.custom is supposed to be used. Version-Release number of selected component (if applicable): redhat-config-bind-2.0.0-14.2 How reproducible: Always Steps to Reproduce: 1. Start redhat-config-bind 2. Make a new zone and save Actual Results: $TTL 86400 primary.nameserver.name. IN SOA localhost root ( 4 ; serial 28800 ; refresh 14400 ; retry 3600000 ; expire 86400 ; ttl ) Expected Results: $TTL 86400 test.domain. IN SOA primary.nameserver.name. root ( 4 ; serial 28800 ; refresh 14400 ; retry 3600000 ; expire 86400 ; ttl ) Additional info:
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.