unable to get a nslookup on windows client

[Danny Mayer]

Niall O'Reilly wrote:
> On 21 Nov 2007, at 22:07, Mark Andrews wrote:
> 
>> 	You mean a couple of bytes of disk space.  The server (named)
>> 	is not started by default.  You have to explicitly start it.
>>
>> 	The full release is on 7860K.  A word document takes more than
>> 	that these days.
> 
> 	Thanks, Mark.
> 
> 	Dealing with the inertia which other people have attached to
> 	themselves is never easy.  Reasone argument doesn't always work!
> 	8-)
> 
> 	Thanks to a couple of people who replied off-list and gave me
> 	pointers to dig-only kits, mentioned below so that others can
> 	find them in the archive.
> 
> 	http://members.shaw.ca/nicholas.fong/dig/
> 	http://serghei.net/windows/dig/
> 
> 	Now for some missionary work on our internal WiKi ...

The one thing at least with the fong reference (I cannot get to the
other one) is that there is no longer a need to create a resolv.conf
file. That issue was fixed quite a while ago. It currently uses the
information that can be found in the registry. Just grab the latest
release of the code.

Danny