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 71043 - Deletion of zones doesn't appear to work
Deletion of zones doesn't appear to work
Product: Red Hat Public Beta
Classification: Retired
Component: redhat-config-bind (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Depends On:
  Show dependency treegraph
Reported: 2002-08-08 01:12 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 01:13:00 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:12:56 EDT
Description of Problem:
With redhat-config-bind-1.7.1-10, the delete button doesn't appear to actually
doing anything "real."

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

How Reproducible:

Steps to Reproduce:
1. Run redhat-config-bind and create a zone file; exit and check /var/named/ to
confirm that the new zone file is present
2. Run redhat-config-bind again and select the new zone
3. Click 'delete'

Actual Results:
Zone file will be deleted from the display, but after exiting from
redhat-config-bind and saving the changes, the zone file will still be present
in /var/named/

Expected Results:

Additional Information:
Comment 1 Daniel Walsh 2002-08-08 09:21:36 EDT
Zone deletion does work.  The entry is removed from /etc/named.conf so the zone
has been eliminated.  The file still exists in the /var/named directory.  I
talked to Jeff Needle who is a support person/System Administrator, and he feels
that he would like the file to stick around.
Comment 2 Jay Turner 2002-08-09 09:10:35 EDT
Indeed, this is the behavior that I'm seeing with redhat-config-bind-1.7.1-12,
so guess that works for me.

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