Bug 10481 - linuxconf creates syntax errors in named.conf
linuxconf creates syntax errors in named.conf
Product: Red Hat Linux
Classification: Retired
Component: linuxconf (Show other bugs)
sparc Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Depends On:
  Show dependency treegraph
Reported: 2000-03-31 11:00 EST by Jason Costomiris
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:47:39 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jason Costomiris 2000-03-31 11:00:22 EST
Yesterday, I installed 6.2 on a Sparc 20 (clean, formatted the
filesystems), which was previously running 6.0, w/bind 8.2.2_p3.

When using linuxconf to add secondaries to DNS on this box, even if you
leave the fields blank for fields such as allow-transfer, allow-query,
allow-update and also-notify, linuxconf creates empty stanzas in the
named.conf, such as:

zone "foo.com"{
        type slave;
        file "sec/foo.com";
        notify no;

bind notes syntax errors in the syslog when it loads.  named starts, but
just whines about the syntax errors.  Previous versions did not do this...
Comment 1 Brent Fox 2002-06-05 12:12:27 EDT
Closing because we don't ship linuxconf anymore
Comment 2 Red Hat Bugzilla 2006-02-21 13:47:39 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.