Bug 561299 - host/nslookup/dig query wrong server
Summary: host/nslookup/dig query wrong server
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: bind
Version: 5.4
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Adam Tkac
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-03 10:32 UTC by Duncan
Modified: 2012-07-27 14:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-13 22:25:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
proposed patch (612 bytes, patch)
2010-02-09 16:17 UTC, Jan Görig
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0032 0 normal SHIPPED_LIVE bind bug fix and enhancement update 2011-01-12 17:22:47 UTC

Description Duncan 2010-02-03 10:32:06 UTC
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.

Comment 1 Jan Görig 2010-02-09 16:17:31 UTC
Created attachment 389793 [details]
proposed patch

Comment 2 Adam Tkac 2010-02-11 15:20:17 UTC
(In reply to comment #1)
> Created an attachment (id=389793) [details]
> proposed patch    

Patch is correct, thank you.

Comment 6 Martin Cermak 2010-10-26 16:54:03 UTC
=> VERIFIED

Comment 9 errata-xmlrpc 2011-01-13 22:25:47 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

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


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