+++ 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