FS#14158 - nslookup and host return NXDOMAIN for every hostname

Attached to Project: Arch Linux
Opened by Stéphane Travostino (eazy) - Thursday, 09 April 2009, 15:32 GMT
Last edited by Jan de Groot (JGC) - Thursday, 23 April 2009, 13:25 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

* package version(s):
- host 20070128-1

---

The two commands 'host' and 'nslookup' return NXDOMAIN for every single host.

$ host xkcd.com
*** xkcd.com does not exist (Authoritative answer)
$ host example.com
*** example.com does not exist (Authoritative answer)
$ host google.com
*** google.com does not exist (Authoritative answer)

Internet and LAN connectivity is OK, no DNS resolution issues whatsoever:

$ telnet google.com 80
Trying 74.125.67.100...
Connected to google.com.

This is /etc/resolv.conf:

$ cat /etc/resolv.conf
# Generated by NetworkManager
domain xxx.loc
search xxx.loc
nameserver 10.52.1.200
nameserver 10.52.1.201

The dump of the DNS request made by host is somewhat strange:

17:26:04.599638 IP 10.52.12.32.50732 > 10.52.1.200.53: 30524+ PTR? 255.255.255.255.in-addr.arpa. (46)
17:26:04.600050 IP 10.52.1.200.53 > 10.52.12.32.50732: 30524 NXDomain* 0/1/0 (130)

While the successful one using telnet:

17:30:11.068638 IP 10.52.12.32.56877 > 10.52.1.200.53: 6308+ AAAA? google.com. (28)
17:30:11.069086 IP 10.52.1.200.53 > 10.52.12.32.56877: 6308 0/1/0 (78)
17:30:11.069190 IP 10.52.12.32.50142 > 10.52.1.200.53: 38994+ AAAA? google.com.xxx.loc. (43)
17:30:11.069580 IP 10.52.1.200.53 > 10.52.12.32.50142: 38994 NXDomain* 0/1/0 (110)
17:30:11.069699 IP 10.52.12.32.58415 > 10.52.1.200.53: 9295+ A? google.com. (28)
17:30:11.070085 IP 10.52.1.200.53 > 10.52.12.32.58415: 9295 3/0/0 A 74.125.45.100,[|domain]
This task depends upon

Closed by  Jan de Groot (JGC)
Thursday, 23 April 2009, 13:25 GMT
Reason for closing:  Fixed
Additional comments about closing:  host has been replaced by dnsutils.
Comment by Stéphane Travostino (eazy) - Thursday, 09 April 2009, 15:33 GMT
Just discovered dnsutils provide 'host'. Installed it and DNS resolution is working:

$ host google.com
google.com has address 74.125.45.100
google.com has address 209.85.171.100
google.com has address 74.125.67.100
Comment by Gerardo Exequiel Pozzi (djgera) - Thursday, 09 April 2009, 16:15 GMT
works for me

[djgera@gerardo ~]$ ./host --version
Host version HOST-20070128, BIND-8 resolver version 19991006, API version: 19991006
[djgera@gerardo ~]$ ./host xkcd.com
xkcd.com A 72.26.203.98

btw: this packages has a problem, is _compiled statically_. (resolver library and other) Maybe in your setup, this old library linked statically has a problem.

Try to recompile "host" throught ABS.
Comment by Jan de Groot (JGC) - Thursday, 09 April 2009, 16:42 GMT
I think it's a good idea to replace host with the working dnsutils package. Static compiled packages are always a pain when glibc nss modules are involved.
Comment by Dirk (dsohler) - Saturday, 18 April 2009, 10:55 GMT
I can confirm this bug!

$ host --version
Host version HOST-20070128, BIND-8 resolver version 19991006, API version: 19991006

$ host archlinux.org
*** archlinux.org does not exist (Authoritative answer)

$ ping -c1 archlinux.org
PING archlinux.org (66.211.213.17) 56(84) bytes of data.
64 bytes from gerolde.archlinux.org (66.211.213.17): icmp_seq=1 ttl=55 time=181 ms

--- archlinux.org ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 181.989/181.989/181.989/0.000 ms

Loading...