Bug 187123 - 'host' and 'dig' don't look up the server address in DNS
'host' and 'dig' don't look up the server address in DNS
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: bind (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Vas Dias
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-03-28 12:06 EST by Russell McOrmond
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-03-28 12:20:53 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Russell McOrmond 2006-03-28 12:06:37 EST
Description of problem:

There is a parameter for both 'host' and 'dig' which can be used to point to a
different nameserver.   While it is possible to use the IPv4 address, it seems
to no longer be possible to specify a hostname.

Version-Release number of selected component (if applicable):
bind-utils-9.3.1-18.FC4
  - Problem only appeared with this very recent update.


How reproducible:  Always


Steps to Reproduce:

Examples using both host and dig.  In the cases where I specify the hostname of
the DNS server I expected to get the same results as when I specify the IP address.

[russell@amadpur ~]>host pns.flora.c
Host pns.flora.c not found: 3(NXDOMAIN)
[russell@amadpur ~]>host pns.flora.ca
pns.flora.ca has address 192.139.46.244
[russell@amadpur ~]>host pns.flora.ca pns.flora.ca
host: couldn't get address for 'pns.flora.ca': failure
[russell@amadpur ~]>host pns.flora.ca 192.139.46.244
Using domain server:
Name: 192.139.46.244
Address: 192.139.46.244#53
Aliases:

pns.flora.ca has address 192.139.46.244
Using domain server:
Name: 192.139.46.244
Address: 192.139.46.244#53
Aliases:

Using domain server:
Name: 192.139.46.244
Address: 192.139.46.244#53
Aliases:

[russell@amadpur ~]>

[russell@amadpur ~]>dig A pns.flora.ca

; <<>> DiG 9.3.1 <<>> A pns.flora.ca
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4040
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;pns.flora.ca.                  IN      A

;; ANSWER SECTION:
pns.flora.ca.           3600    IN      A       192.139.46.244

;; AUTHORITY SECTION:
flora.ca.               3600    IN      NS      pns.flora.ca.
flora.ca.               3600    IN      NS      sns.flora.ca.

;; ADDITIONAL SECTION:
sns.flora.ca.           3600    IN      A       192.139.46.131

;; Query time: 2 msec
;; SERVER: 192.168.168.254#53(192.168.168.254)
;; WHEN: Tue Mar 28 12:09:14 2006
;; MSG SIZE  rcvd: 94

[russell@amadpur ~]>dig A pns.flora.ca @pns.floraca
dig: couldn't get address for 'pns.floraca': failure
[russell@amadpur ~]>dig A pns.flora.ca @192.139.46.244

; <<>> DiG 9.3.1 <<>> A pns.flora.ca @192.139.46.244
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25042
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;pns.flora.ca.                  IN      A

;; ANSWER SECTION:
pns.flora.ca.           3600    IN      A       192.139.46.244

;; AUTHORITY SECTION:
flora.ca.               3600    IN      NS      pns.flora.ca.
flora.ca.               3600    IN      NS      sns.flora.ca.

;; ADDITIONAL SECTION:
sns.flora.ca.           3600    IN      A       192.139.46.131

;; Query time: 119 msec
;; SERVER: 192.139.46.244#53(192.139.46.244)
;; WHEN: Tue Mar 28 12:09:26 2006
;; MSG SIZE  rcvd: 94

[russell@amadpur ~]>
Comment 1 Russell McOrmond 2006-03-28 12:20:53 EST
Apologies:  I noticed the same problem with other tools, and looked elsewhere. 
Seems that my old /etc/nsswitch.conf was referencing 'nisplus' which is not there.  

A simple:  `mv nsswitch.conf.rpmnew nsswitch.conf`  in /etc/ to use the new
default config file ended up fixing the problem.


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