Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 3234 - dnsquery, route, unable to resolve anything
Summary: dnsquery, route, unable to resolve anything
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: bind
Version: 6.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Cristian Gafton
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 1999-06-03 10:16 UTC by tom
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 1999-08-19 21:57:55 UTC

Attachments (Terms of Use)

Description tom 1999-06-03 10:16:10 UTC
dnsquery is unable to look up addresses without help, eg:

[tom@skybowl tom]$ dnsquery
Query failed (h_errno = 2) : Host name lookup failure

If I specify a nameserver it's able to use DNS (it's even
the same DNS server that's listed in /etc/resolv.conf).

[tom@skybowl tom]$ dnsquery -n
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26208
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 3,
;;, type = ANY, class = IN		48m41s IN NS		48m41s IN NS		48m41s IN NS		48m38s IN A		48m38s IN MX	10		48m38s IN MX	5		48m41s IN NS		48m41s IN NS		48m41s IN NS		1d13h25m49s IN A	5h37m12s IN A	48m11s IN A  48m38s IN A

A utility such as host still works fine without help:
[tom@skybowl tom]$ host has address mail is handled (pri=10) by mail is handled (pri=5) by

As a side effect I also note that 'route' isnt able to
resolve hosts:

[tom@skybowl tom]$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric
Ref    Use Iface    *      UH    0
0        0 eth0    *        U     0
0        0 eth0       *            U     0
0        0 lo
default         UG    0
0        0 eth0

Comment 1 Jeff Johnson 1999-06-06 16:20:59 UTC
I'm changing the component to bind because that's the package that
contains dnsquery.

Route resolves hostnames quite well, even in your example. Perhaps
your DNS needs some attention ...

Comment 2 tom 1999-06-06 16:38:59 UTC
erg (don't submit bugs late at night I think is the moral) in regards
my route embarrassment. However, dnsquery is definitely buggy.

The RedHat 5.2 machines are able to use dnsquery, but not the 6.0

Comment 3 Jay Turner 1999-06-29 11:29:59 UTC
Confirmed the dnsquery problem in the test lab.

Comment 4 Jay Turner 1999-06-29 11:30:59 UTC
Confirmed the dnsquery problem in the test lab.

Comment 5 Bill Nottingham 1999-08-19 21:57:59 UTC
works OK with the latest dnsquery from bind in Raw Hide.

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