Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1389786 - [RFE] Samba add 'net ads dns unregister' command from Samba 4.5.0
[RFE] Samba add 'net ads dns unregister' command from Samba 4.5.0
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: samba (Show other bugs)
7.2
All Linux
urgent Severity urgent
: rc
: ---
Assigned To: Andreas Schneider
Robin Hack
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-10-28 11:29 EDT by Amy Farley
Modified: 2017-08-01 14:19 EDT (History)
13 users (show)

See Also:
Fixed In Version: samba-4.6.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-01 14:19:59 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1950 normal SHIPPED_LIVE Low: samba security, bug fix, and enhancement update 2017-08-01 14:09:24 EDT

  None (edit)
Comment 1 Amy Farley 2016-10-28 12:07:40 EDT
Samba 4.5.0 added 'net ads dns unregister' command to unregister DNS entries.  This would be very useful for us in our environment.

https://lists.samba.org/archive/samba-technical/2016-March/112748.html

The patch is pretty straight forward.  I was able to backport it to the RHEL6.8 Samba 3 very easily and it is working there.  No point in requesting it for RHEL 6 at this point, so we are only requesting this for RHEL7.

We plan to migrate to RHEL7 at the beginning of CY2017 and this would be helpful.  We will also me migrating all workstations and servers to a new AD domain.   Having this features simplifies the migration process for us significantly.
Comment 14 errata-xmlrpc 2017-08-01 14:19:59 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:1950

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