My /etc/resolv.conf is set up as so: [minter@squirtle minter]$ cat /etc/resolv.conf search raleigh.netraverse.com netraverse.com nameserver 216.5.103.195 [minter@squirtle minter]$ I'm trying to do a dig on host "zephyr.raleigh.netraverse.com". Running "dig zephyr" gives: [minter@squirtle minter]$ dig zephyr ; <<>> DiG 9.1.0b1 <<>> zephyr ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32164 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 ;; QUESTION SECTION: ;zephyr. IN A ;; AUTHORITY SECTION: . 9781 IN SOA A.ROOT-SERVERS.NET. hostmaster.nsiregistry.NET. 2000122701 1800 900 604800 86400 ;; Query time: 11 msec ;; SERVER: 216.5.103.195#53(216.5.103.195) ;; WHEN: Thu Dec 28 12:32:42 2000 ;; MSG SIZE rcvd: 100 Running "dig zephyr.raleigh.netraverse.com" gives: [minter@squirtle minter]$ dig zephyr.raleigh.netraverse.com ; <<>> DiG 9.1.0b1 <<>> zephyr.raleigh.netraverse.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27929 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3 ;; QUESTION SECTION: ;zephyr.raleigh.netraverse.com. IN A ;; ANSWER SECTION: zephyr.raleigh.netraverse.com. 432000 IN A 216.5.103.194 ;; AUTHORITY SECTION: raleigh.netraverse.com. 432000 IN NS ns1.netraverse.com. raleigh.netraverse.com. 432000 IN NS ns2.netraverse.com. raleigh.netraverse.com. 432000 IN NS ns3.netraverse.com. ;; ADDITIONAL SECTION: ns1.netraverse.com. 432000 IN A 216.5.96.90 ns2.netraverse.com. 432000 IN A 216.5.96.85 ns3.netraverse.com. 432000 IN A 216.5.103.195 ;; Query time: 13 msec ;; SERVER: 216.5.103.195#53(216.5.103.195) ;; WHEN: Thu Dec 28 12:33:30 2000 ;; MSG SIZE rcvd: 187 nslookup does the same type thing. It appears that dig/nslookup aren't using the search path from resolv.conf.
dig is not supposed to append domains out of /etc/resolv.conf, but nslookup is.
Still present in 0.b3.1
This defect is considered MUST-FIX for Florence Gold release
I failed to reproduce this problem with bind-utils-9.1.0-2. nslookup and host use the search entry in /resolv.conf and the domain part of the hostname. dig isn't supposed to use the search entry in resolv.conf, it uses only the DNS information from that file. I suggest to close this report as 'not a bug'
Confirmed to be working with bind-utils-9.1.0-1.