Re: Microsoft DNS Client Service

[prev] [thread] [next] [lurker] [Date index for 2004/09/03]

From: peter (Peter da Silva)
Subject: Re: Microsoft DNS Client Service
Date: 15:36 on 03 Sep 2004
> Is it 'intercepting', or are the hostname resolution routines using
> other sources first, much as Suns will use NIS+ maps, etc etc?

If you stop the service, name resolution through other source (WINS,
etc) still works, and DNS requests start working as expected. Among
other things, the DNS Client service ignores the name server order,
caches failures, and returns WINS and browsed names for unqualified
hostnames... which is fun when someone changes the name of his
laptop to same name as some non-windows server people are using
from Windows.

> If it's cached a failure, have you tried ipconfig /flushdns, that
> ever-so-handy tool for dealing with the broken cache-timeouts in the MS
> name-service cache?

No, I didn't know about that one, and I'm glad I didn't, because
then I'd have had people do that instead of just turning the service
off. I have had zero problems reported due to people turning it
off, and no repeat complaints due to any of the above problems.
Near as I can tell the only legitimate use for this service is to
let people get some kind of DNS in an environment where DNS is
broken or nonexistent (eg, on a Windows-only Workgroup or NT4
Domain).

There's stuff above here

Generated at 16:01 on 03 Sep 2004 by mariachi 0.52