Bug 700097 - nsupdate returns success when target zone does not exist
Summary: nsupdate returns success when target zone does not exist
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: bind
Version: 6.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Adam Tkac
QA Contact: Juraj Marko
URL:
Whiteboard:
Depends On:
Blocks: 690473 731950 744141
TreeView+ depends on / blocked
 
Reported: 2011-04-27 12:51 UTC by Martin Kosek
Modified: 2015-09-01 03:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 731950 744141 (view as bug list)
Environment:
Last Closed: 2011-12-06 17:26:29 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1697 0 normal SHIPPED_LIVE bind bug fix update 2011-12-06 01:02:33 UTC

Description Martin Kosek 2011-04-27 12:51:51 UTC
Description of problem:

nsupdate command returns success when the update fails because of missing zone.

Version-Release number of selected component (if applicable):
bind-utils-9.7.3-2.el6.x86_64

How reproducible:

This was reproduced in FreeIPA client installation where client hostname was set under an invalid DNS zone:

# cat .nsupdate 
zone bar.
update delete foo.bar. IN A
send
update add foo.bar. 1200 IN A 10.16.78.134
send

# nsupdate -g .nsupdate
specified zone 'bar' does not exist (NXDOMAIN)
specified zone 'bar' does not exist (NXDOMAIN)
specified zone 'bar' does not exist (NXDOMAIN)

# echo $?
0

Steps to Reproduce:
1. Create .nsupdate file as stated above
2. Pass it to nsupdate
3. Check exit code
  
Actual results:
Returns success

Expected results:
Returns error value

Comment 7 errata-xmlrpc 2011-12-06 17:26:29 UTC
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.

http://rhn.redhat.com/errata/RHBA-2011-1697.html


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