Re: resolver, search command....

2013-05-08 Thread Sten Carlsen
You probably want to use host myhost, that does use the resolv.conf as the system normally would. And it works better than nslookup. On 08/05/13 16:56, Evan Hunt wrote: >> dig myhost > By default dig only uses fully qualified domain names. "dig +search" > does what you want. > >> It would search f

Re: resolver, search command....

2013-05-08 Thread Evan Hunt
> dig myhost By default dig only uses fully qualified domain names. "dig +search" does what you want. > It would search for that host in path1 or path2 listed above.? It does > not, a +trace shows the resolver querying the root servers for myhost.? > So it appears the search command does not work

Re: resolver, search command....

2013-05-08 Thread Chris Thompson
On May 8 2013, John Williams wrote: my resolv.conf looks like nameserver 10.10.10.10 nameserver 10.10.10.20 search path1.mydomain.com path2.mydomain.com I would expect if I type the following: dig myhost It would search for that host in path1 or path2 listed above. It does not, a +trac

Re: resolver, search command....

2013-05-08 Thread Matthew Horsfall (alh)
On 05/08/2013 10:32 AM, John Williams wrote: > my resolv.conf looks like > > nameserver 10.10.10.10 > nameserver 10.10.10.20 > search path1.mydomain.com path2.mydomain.com > > I would expect if I type the following: > > dig myhost You want dig +search myhost By default it ignores the sear

resolver, search command....

2013-05-08 Thread John Williams
my resolv.conf looks  like nameserver 10.10.10.10 nameserver 10.10.10.20 search path1.mydomain.com path2.mydomain.com I would expect if I type the following: dig myhost It would search for that host in path1 or path2 listed above.  It does not, a +trace shows the resolver querying the root