Re: DNS not doing recursive lookups
- From: "Rob Boylan" <RobBoylan@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 15 Aug 2005 20:29:07 -0700
Thanks for your help Ace.
"Ace Fekay [MVP]" wrote:
> One is your AD domain name is possibly a single label domain name? It should
> be in the form of the TLD plus the first level name, such as example.com. I
> hope you were just trying to mask the names and you do not have a single
> label name.
Actually, I do have a single-label domain name. This place really is a TLD.
If I understand the <a
href="http://support.microsoft.com/?kbid=300684">knowledge base article</a>
correctly, there are two things that do not work automatically in a single
label domain: 1) dynamic updates do not work and 2) member computers cannot
use DNS to locate DCs in a single-label domain that is in another forest. I'm
not planning on allowing dynamic updates in this domain and I'm not dealing
with multiple forests. So is there another gotcha that I'm overlooking?
> Second, there is NO need for manually creating any records in the
> netlogon.dns file for AD. This is an automatic process. The netlogon
> services updates the netlogon.dns file from what it reads in AD, then it
> sends that data to the zone name configured in the Primary DNS Suffix using
> the DNS address listed in it's IP properties. If this is not working
> automatically, then there is a major configuration problem. A single label
> domain name will cause this not to function.
Netlogon is not doing this automatically. I had assumed that this was
because dynamic DNS was disabled.
>
> Third, the inability for Win2003 to resolve external names without a
> forwarder is possibly due to your Cisco router. Windows 2003 is now using a
> new industry standard feature called EDNS0 that allows UDP DNS queries to go
> beyond the previously capped limit of 512 bytes to the max 1500 MTU. To fix
> it, either update the Cisco firmware (which is the recommendation), or
> disable it in Win2003.
>
> 828731 - An External DNS Query May Cause an Error Message in Windows Server
> 2003:
> http://support.microsoft.com/?id=828731
The Cisco link on this page goes to a "Page Not Found". Searching the Cisco,
site I could not find anything that seemed to mention increasing the
allowable UDP packet size. Does this require a firmware upgrade or just an
upgrade to the IOS? Which versions have the required modification? I'll need
to find firm documentation before I'll be allowed to make changes to the
routers.
In the meantime, I will try disabling the EDNS0 on the Windows 2003 server,
although I will have to wait for a non-peek usage time to perform the test.
Thanks,
--Rob
.
- Follow-Ups:
- Re: DNS not doing recursive lookups
- From: Ace Fekay [MVP]
- Re: DNS not doing recursive lookups
- References:
- DNS not doing recursive lookups
- From: Rob Boylan
- Re: DNS not doing recursive lookups
- From: Ace Fekay [MVP]
- DNS not doing recursive lookups
- Prev by Date: Re: Old Domains Still Show in Logon Field
- Next by Date: Unable to resolve MX using nslookup
- Previous by thread: Re: DNS not doing recursive lookups
- Next by thread: Re: DNS not doing recursive lookups
- Index(es):
Relevant Pages
|
Loading