host from BIND 9.4.1-P1 is confused by multiple search options in /etc/resolv.conf

[Kevin Darcy]

man resolv.conf.

You can only effectively have 1 "search" directive, but it can have 
multiple elements.

Searchlists are generally a bad idea, though. Teach your users to use 
fully-qualified domain names.

                                                 - Kevin

Joseph S wrote:
> The host command appears to only want to use the last search option in 
> /etc/resolv.conf.
>
> On a rehdat machine:
>
> [jks at c1 ~]$ cat /etc/resolv.conf
>
> search selectacast.net
> search xtenit.com
> #
> nameserver 199.107.233.222
>
> [jks at c1 ~]$ /usr/local/bin/host -v p8
> Trying "p8.xtenit.com"
> Trying "p8"
> Host p8 not found: 3(NXDOMAIN)
> Received 95 bytes from 199.107.233.222#53 in 0 ms
> [jks at c1 ~]$ /usr/bin/host -v p8
> Trying "p8.selectacast.net"
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33952
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4
>
> ;; QUESTION SECTION:
> ;p8.selectacast.net.            IN      A
>
> ;; ANSWER SECTION:
> p8.selectacast.net.     3600    IN      A       199.107.233.218
>
> ;; AUTHORITY SECTION:
> selectacast.net.        3600    IN      NS      ns.selectacast.net.
> selectacast.net.        3600    IN      NS      ns2.selectacast.net.
> selectacast.net.        3600    IN      NS      ns-east.cerf.net.
> selectacast.net.        3600    IN      NS      ns-west.cerf.net.
>
> ;; ADDITIONAL SECTION:
> ns.selectacast.net.     3600    IN      A       199.107.233.222
> ns2.selectacast.net.    3600    IN      A       63.240.50.214
> ns-east.cerf.net.       162716  IN      A       207.252.96.3
> ns-west.cerf.net.       162716  IN      A       192.153.156.3
>
> Received 200 bytes from 199.107.233.222#53 in 4 ms
> [jks at c1 ~]$ rpm -q bind-utils
> bind-utils-9.2.4-27.0.1.el4
>
>
>
>
>
>