Bug 816166

Summary:	nslookup exits with zero return value when DNS server is not accessible
Product:	[Fedora] Fedora	Reporter:	Jan Stodola <jstodola>
Component:	bind	Assignee:	Adam Tkac <atkac>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16	CC:	atkac, ovasik
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	816164	Environment:
Last Closed:	2012-05-22 09:27:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan Stodola 2012-04-25 11:54:47 UTC

+++ This bug was initially created as a clone of Bug #816164 +++

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

Comment 1 Jan Stodola 2012-04-25 11:55:47 UTC

Also reproduced on F16, bind-utils-9.8.2-0.4.rc2.fc16.x86_64

Comment 2 Adam Tkac 2012-05-22 09:27:06 UTC

Fixed in bind-9.9.0-6.fc18. Fix will be backported to F17 but I'm not going to fix this issue in Fedora 16.