Bug 561299

Description of problem:

I have noticed that release 5.4 (Final) appears to ignore the server option when
using host or nslookup if the host in question is not available.

The commands should return no server available as they have in the past
but instead decide to query the servers specified in resolv.conf and return results from that.

# nslookup google.co.uk 123.123.123.1
Server:         127.0.0.1
Address:        127.0.0.1#53

Non-authoritative answer:
Name:   google.co.uk
Address: 66.102.11.99
Name:   google.co.uk
Address: 66.102.11.104

The correct response should be

# nslookup google.co.uk 123.123.123.1
;; connection timed out; no servers could be reached

Version-Release number of selected component (if applicable):

9.3.6-4.P1.el5_4.2

How reproducible:

As above, run a host or nslookup command and specify the optional server to query making sure its one which won't return a result.

Actual results:

query returns results from server in resolv.conf (in this case 127.0.0.1) when the server specified is unreachable.

Expected results:

Should return ;; connection timed out; no servers could be reached

Additional info:

Works fine in Fedora 4,8,9 and 11, Red Hat Enterprise Linux ES release 4 release 4 (Nahant Update 8) and Red Hat Enterprise Linux Server release 5.1 (Tikanga)

Fails in 5.4 and Fedora 10.