Bug 816164 - nslookup exits with zero return value when DNS server is not accessible
nslookup exits with zero return value when DNS server is not accessible
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: bind (Show other bugs)
6.3
All Linux
high Severity high
: rc
: ---
Assigned To: Adam Tkac
qe-baseos-daemons
:
Depends On:
Blocks: 756608 760559 829243 829829
  Show dependency treegraph
 
Reported: 2012-04-25 07:48 EDT by Jan Stodola
Modified: 2012-07-27 10:56 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 816166 829243 829829 (view as bug list)
Environment:
Last Closed: 2012-06-20 09:41:20 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)

  None (edit)
Description Jan Stodola 2012-04-25 07:48:39 EDT
Description of problem:
nslookup exits with zero return value even when a query fails (DNS server doesn't respond): 

[root@rtt5 ~]# rpm -qf `which nslookup`
bind-utils-9.8.2-0.7.rc1.el6.s390x
[root@rtt5 ~]# nslookup 11.22.33.44 172.16.1.1
;; connection timed out; trying next origin
;; connection timed out; trying next origin
;; connection timed out; trying next origin
;; connection timed out; no servers could be reached

[root@rtt5 ~]# echo $?
0

Compare with the "host" command:
[root@rtt5 ~]# host 11.22.33.44 172.16.1.1
;; connection timed out; no servers could be reached
[root@rtt5 ~]# echo $?
1

Version-Release number of selected component (if applicable):
bind-utils-9.8.2-0.7.rc1.el6

How reproducible:
always

Steps to Reproduce:
1. nslookup 11.22.33.44 172.16.1.1
2. echo $?
  
Actual results:
0

Expected results:
non-zero value

Additional info:
This bug blocks verification of bug 756608, proposing as a blocker.
Comment 7 errata-xmlrpc 2012-06-20 09:41:20 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.

http://rhn.redhat.com/errata/RHBA-2012-0830.html

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