Re: Weird DNS issue
- From: "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx>
- Date: Wed, 10 Aug 2005 23:53:55 -0400
In news:5D8E1862-8920-4A8A-B9DF-DC9226C3FC4D@xxxxxxxxxxxxx,
-Nick <Nick@xxxxxxxxxxxxxxxxxxxxxxxxx> made this post, which I then
commented about below:
> OK, So your saying the clients should only have the local DNS address
> in their configuration? I understand how that would work, but what I
> don't understand is why it shouldn't work the way we have it setup
> right now.
Nick,
The reason is based on the DNS client side resolver. Each machine, including
the DNS server, has a client side resolver service that is controlled by the
DHCP Client service. And yes, the name of that service does not make sense
to what it really is doing but believe me, that's what that service does. If
you turn it off, nothing gets resolved nor do dynamic registrations work.
As for the client side resolver behavior, if there are multiple DNS entries
on a machine (whether a DC, member server or client), it will ask the first
entry first. If it times out on the response, it will go to the second
entry, but it REMOVES the first entry from the eligible resolvers list, and
won't go back to it. This can cause issues within AD when accessing a
resource such as a printer, folder, getting GPOs to function, etc. Another
good reason to ONLY use the internal DNS server.
Querying DNS Servers - how the resolver service works:
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/winxppro/reskit/prjj_ipa_bsmz.asp
Recommended "best practice" to insure full AD and client functionality:
Point all machines ONLY to the internal server(s), and configure a forwarder
to your ISP's DNS. This way all machines query your DNS and if it doesn't
have the answer, it asks outside. If the forwarding option is grayed out,
delete the root zone, (it looks like a period), refresh the console, and try
again. If not sure how to configure this, these articles will guide you thru
it:
323380 - HOW TO Configure DNS for Internet Access in Windows Server 2003 :
http://support.microsoft.com/?id=323380
300202 - HOW TO Configure DNS for Internet Access in Windows Server 2000 :
http://support.microsoft.com/?id=300202
Also, for your reading pleasure...
825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003:
http://support.microsoft.com/default.aspx?scid=kb;en-us;825036
DNS and AD (Windows 2000 & 2003) FAQ:
http://support.microsoft.com/?id=291382
--
Regards,
Ace
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.
This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Infinite Diversities in Infinite Combinations.
=================================
.
- References:
- Weird DNS issue
- From: -Nick
- Re: Weird DNS issue
- From: Frankster
- Re: Weird DNS issue
- From: -Nick
- Re: Weird DNS issue
- From: Frankster
- Re: Weird DNS issue
- From: -Nick
- Weird DNS issue
- Prev by Date: Re: Windows 2003 server DNS problems
- Next by Date: Cannot Access Web Site using TLD internally?
- Previous by thread: Re: Weird DNS issue
- Next by thread: DNS auto entry nightmare
- Index(es):
Relevant Pages
|
Loading
