DNS client service missing

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

On a 2000 Domain Controller in a 2000 domain, one of the DC have no DNS client service. It is missing from the services snap-in. Can't resolve any SRV records or anything else locally, but It can connect to the internet via URLs. Any hints on how to get the service back. I would really prefer not to reinstall. This is a new job for me and the previous Sys Admin did no backups, so restore from backup is not possible.
 
physicsgeek said:
On a 2000 Domain Controller in a 2000 domain, one of the DC have no DNS
Click to expand...
client service. It is missing from the services snap-in. Can't resolve any
SRV records or anything else locally, but It can connect to the internet via
URLs. Any hints on how to get the service back. I would really prefer not to
reinstall. This is a new job for me and the previous Sys Admin did no
backups, so restore from backup is not possible.

Ok, wait a minute. The DNS Client service is NOT
required to resolve DNS names (yes, I know that's
what it SOUNDS like.)

If you can resolve names on the Internet but not
internally you have a CONFIGURATION problem
on the DCs NICs -- see below -- not a problem
with the DNS client service.

The DNS client service is worthless, probably counterproductive
if it runs on a DNS server (that references itself as a
DNS-client=>DNS-server

The DNS client service should be called the "DNS client cache";
and on a DNS server, which caches itself, you would just be
duplicating the cache and taking up more memory and time
searching it.

Make sure the DCs client NIC configuration points to the INTERNAL
DNS -- and NO OTHER. Restart NetLogon after you fix this.

If you have a multihomed DC -- especially with a DHCP assigned
address (using it as a gateway) you must ensure that it does NOT
end up with a DNS server setting that points OUTSIDE.

DHCP clients can override that setting with an internal DNS
server and still accept everything else from DHCP.
 
In
Herb Martin said:
The DNS client service should be called the "DNS client cache";
and on a DNS server, which caches itself, you would just be
duplicating the cache and taking up more memory and time
searching it.
Click to expand...

Actually in the registry, that's what it's called.

<snip>

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In Ace Fekay [MVP] <PleaseSubstituteMyActualFirstName&[email protected]>
posted their thoughts, then I offered mine

In addition, iuf you are having problems with nothing resolving, and
provided your configuration is correct, pointing to your own DNS only,
forwarders configured, etc, I would also make sure that the DHCP Client
Service is running. This service, is an ABSOLUTE MUST to be running, whether
your machine is set to DHCP or a static address. If this service is not
running, the machine will resolve nothing.

This service is not like the DNS Client service, where Herb explains that it
just offers caching services, that's it. DHCP Client service is a MUST.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Herb Martin said:
And it is a MISNOMER -- a poorly chosen name.
Click to expand...

Just to make sure we're on the same page, if you mean DNS Cache, I think
that's a descriptive name, but if you mean DNS Client service, I agree. In
the reg it's called DNS Cache.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
And it is a MISNOMER -- a poorly chosen name.
Just to make sure we're on the same page, if you mean DNS Cache, I think
that's a descriptive name, but if you mean DNS Client service, I agree. In
the reg it's called DNS Cache.
Click to expand...

Oh, I thought you meant it was called by the same name
in the registry, as the display name for it (that's in there
too of course.)

One of the important things I teach my students is when
the "names" are poorly choose, e.g.,

superscopes (scope groups)
ad client upgrade/DSClient (legacy client support)
site link bridging (site link groups)
PDC Emulator (correct but incomplete)
 
In
Herb Martin said:
Oh, I thought you meant it was called by the same name
in the registry, as the display name for it (that's in there
too of course.)
Click to expand...

Nah, it's just the display name.
One of the important things I teach my students is when
the "names" are poorly choose, e.g.,

superscopes (scope groups)
ad client upgrade/DSClient (legacy client support)
site link bridging (site link groups)
PDC Emulator (correct but incomplete)
Click to expand...

Good point to understand what it does even though it has nothing to do with
the name.



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
One of the important things I teach my students is when
Good point to understand what it does even though it has nothing to do with
the name.
Click to expand...

Especially when the name LOOKS like it means one thing
but means something skewed or even the opposite.

Another pure name: "Mixed mode" -- it makes too many
people think of "mixed networks of different client types"
and then you spend serious time having to unlearn that
assumption.
 
In
Herb Martin said:
Especially when the name LOOKS like it means one thing
but means something skewed or even the opposite.

Another pure name: "Mixed mode" -- it makes too many
people think of "mixed networks of different client types"
and then you spend serious time having to unlearn that
assumption.
Click to expand...

Yes, there are others as well, like the 'Do Not Use Recursion' checkbox
under Forwarders tab.

:-)



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Yes, there are others as well, like the 'Do Not Use Recursion' checkbox
under Forwarders tab.
Click to expand...

OOOOHHHH, how could I have neglected to mention that
egregious example in such a list.

Actually, that one is ok, though. It's the partner setting under
"Advanced" that was WRONG. They corrected it in Win2003
DNS server though.
 
Back
Top