Re: DNS Client Config
- From: Meinolf Weber <meiweb(nospam)@gmx.de>
- Date: Wed, 5 Nov 2008 19:21:16 +0000 (UTC)
Hello Barry,
This states, NOT to configure the ISP's DNS server on the NIC. What else do you need?
"If this server needs to resolve names from its Internet service provider (ISP), you must configure a forwarder."
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Thanks, but that doesn't really spell it out. I am having a hard time
finding something that says never set a secondary DNS server on a
Windows domain client to an external DNS server. I need something I
can show that says only use internal DNS servers and this is why you
don't use external.
"Meinolf Weber" wrote:
Hello Barry,
See here:
http://support.microsoft.com/kb/323380
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
I am looking for a white paper that says in plain English that when
setting up DHCP, you don't need to add the ISP's DNS server as a
secondary DNS. It is best to use one of the many internal DNS's,
and then use forwarders. I can't seem to find a document that
spells that out. This is in a medium sized AD environment.
.
- Follow-Ups:
- Re: DNS Client Config
- From: Barry Alan
- Re: DNS Client Config
- References:
- Re: DNS Client Config
- From: Barry Alan
- Re: DNS Client Config
- Prev by Date: Re: DNS Client Config
- Next by Date: Re: Bringing DNS In-house
- Previous by thread: Re: DNS Client Config
- Next by thread: Re: DNS Client Config
- Index(es):
Relevant Pages
|