In
seeking assistance said:
Yes the 2000 has the DNS server, a reminent of the 2000 domain
upgrade. The domain is at 2003 now (mixed mode). I am attempting to
get rid of the 2000 DCs.
So the installation process on the 2003 was add remove programs,
windows componets, add DNS from the 2003 CD. I was able to see the
DNS entries. However in the right hand side of the DNS explorer
window it said the server was not configured. This concerned me so I
started this thread. Since then I have removed DNS, and readded it
through the server manager and adding a role. Same results. I then
went to a 2000 DNS server and connected to the new 2003 DNS server.
The new server was not listed, so I connected to it from that DNS
server, rt click configure server (I think going off memory) selected
AD integrated, ok. Server showed up in the list. I then went back
to the 2003 server and the right hand side of the DNS explorer window
showed the forward and reverse lookup zones. It seemed to have
configured that server. I have one more 2003 DNS server to
configure, I havent started yet. How do you think I should proceed?
Thanks
Cody
Hello Cody,
In addition to the DNS configuration you and Meinolf are discussing (please
follow his recommendations for this), the main problem causing replication
and other problems, is the single label name domain. This has been a major
issue with AD DNS domain names since Win2000 SP4. After Win2000 SP4 and
later, Microsoft stopped the ability for a machine to register into a single
label name zone. Try applying the following patch on ALL machines (DCs and
clients) to get through this until you get a chance to change the name or
migrate to a new domain in a new forest with a proper DNS name (such as
bf.net, etc). A single label domain is considered a TLD (such as com, edu,
net, etc), and DNS has difficulty with it, because it considers it a TLD and
will query the roots first before even looking at itself even though it
hosts the zone.
If you need assistance with renaming (need minimum of Windows 2003) or
migration, please post back.
Use this patch/bandaid for ALL machines:
300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names:
http://support.microsoft.com/?id=300684
FYI, here is more info on why it was stopped by Microsoft.
======================================================================================================
======================================================================================================
Single label name from Alan Woods, MS:
"We really would preffer to use FQDN over Single label name. There are
alot of other issues that you can run into when using a Single labeled
domain name with other AD integrated products. Exchange would be a great
example. Also note that the DNR (DNS RESOLVER) was and is designed to
Devolve DNS requests to the LAST 2 names.
Example: Single Labeled domain .domainA
then, you add additional domains on the forest.
child1.domainA
Child2.child1.domainA
If a client in the domain Child2 wants to resolve a name in domainA
Example. Host.DomainA and uses the following to connect to a share
\\host then it is not going to resolve. WHY, because the resolver is
first going to query for first for Host.Child2.child1.domainA, then it
next try HOST.Child1.domainA at that point the Devolution process is
DONE. We only go to the LAST 2 Domain Names.
Also note that if you have a single labeled domain name it causes excess
DNS traffic on the ROOT HINTS servers and being all Good Internet Community
users we definitely do not want to do that. NOTE that in Windows 2003,
you get a big Pop UP Error Message when trying to create a single labeled
name telling you DON'T DO IT. It will still allow you to do it, but you
will still be required to make the registry changes, which is really not
fun.
Microsoft is seriously asking you to NOT do this. We will support you but
it the end results could be limiting as an end results depending on the
services you are using.
Thank you,
Alan Wood[MSFT]"
======================================================================================================
======================================================================================================
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(e-mail address removed)
For urgent issues, you may want to contact Microsoft PSS directly. Please
check
http://support.microsoft.com for regional support phone numbers.