[159749] in North American Network Operators' Group
RE: Intermittent incorrect DNS resolution?
daemon@ATHENA.MIT.EDU (Keith Medcalf)
Sun Jan 20 00:23:53 2013
Date: Sat, 19 Jan 2013 22:23:35 -0700
In-Reply-To: <50F9CF94.2030202@abellohome.net>
From: "Keith Medcalf" <kmedcalf@dessus.com>
To: "Vinny Abello" <vinny@abellohome.net>,
"Jay Ashworth" <jra@baylink.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> Just an FYI...
>
> Every version of Windows since Windows 2000 (sans Windows Me) has had
> the DNS Client service which maintained this caching function. This w=
as
> by design due to the massive dependency on DNS resolution which Activ=
e
> Directory has had since its creation. It greatly reduced the amount o=
f
> repetitive lookups required thereby speeding up AD based functions an=
d
> lessening the load on DNS servers. It still exists today up through
> Windows 8. You can disable the service, but it will also break DDNS
> updates unless your DHCP server registers hostnames on behalf of your
> clients.
>
> - -Vinny
DDNS updates (including WINS registrations), static updates, and Active=
Directory registrations are handled by the DHCPClient service since Wi=
ndows 95 through all versions of client and server since. The DNSClien=
t handles caching (in a method somewhat akin a very broken caching-only=
nameserver) only. You can disable the DNSClient service with no ill e=
ffect at all (actually, it will probably improve things significantly, =
if you have a local non-Windows caching recursive DNS to use). You can=
not disable the DHCPClient service, however, without breaking DDNS upda=
tes, static configuration, and Active Directory.
---
() ascii ribbon campaign against html e-mail
/\ www.asciiribbon.org
