Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 71042 - Wrong field getting written as primary nameserver
Wrong field getting written as primary nameserver
Product: Red Hat Public Beta
Classification: Retired
Component: redhat-config-bind (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Daniel Walsh
Depends On:
  Show dependency treegraph
Reported: 2002-08-08 01:09 EDT by Jay Turner
Modified: 2015-01-07 18:58 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-08-08 09:48:26 EDT
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 Jay Turner 2002-08-08 01:09:42 EDT
Description of Problem:
With redhat-config-bind-1.7.1-10, it appears that the contact field is actually
getting written to the zone file as the primary nameserver.

Version-Release number of selected component (if applicable):

How Reproducible:

Steps to Reproduce:
1. Run redhat-config-bind
2. Create a forward master zone and save it
3. Now look at the resulting zone file in /var/named/

Actual Results:
You will something like the following:
$TTL 86400
@       IN      SOA       root.localhost (
                        1 ; serial

Where you can see that "root.localhost" has been written as the primary
nameserver (SOA record.)

Expected Results:

Additional Information:
Comment 1 Daniel Walsh 2002-08-08 09:48:21 EDT
It seems like you are saving the forward zone without entering a Primary
Nameserver (SOA).  How are you doing this?  I can not duplicate this here.

Comment 2 Jay Turner 2002-08-09 09:08:29 EDT
Yeah, pretty much I was being stupid.  I didn't realize that you weren't
requiring "@" in the SOA record anymore, so it wasn't getting accepted and it
was really late and I didn't quite realize what was happening :-)  Things appear
to be working pretty well with redhat-config-bind-1.7.1-12.

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