Re: About DNS naming convention for Active Directory

In news:yNaUUizaFHA.3336@xxxxxxxxxxxxxxxxxxxxx,
"Rebecca Chen [MSFT]" <v-rebc@xxxxxxxxxxxxxxxxxxxx> stated, and I replied below: 
Hello,

I am glad to see you here and this the correct place to discuss the
DNS issue. We can share the experience from other partners, such as
Ace's excellent reply. :)

I would like to add some cents regarding Ace's question about your
questions.

a) Is it necessary to use our Internet domain name as Domain Name for
Active Directory? At the moment, I'm using something like:
corporate.companynamelocal.com for the first AD in the forest. We do 
have a public Internet domain name (i.e. companyname.com) but >not
sure if this is necessary.  For the rest of the AD in the forest,
what naming convention should I use?  Most likely, we'll have one AD
per physical building. 

I have discussed this question with other partner for several times.
You can use the same name or the different name, however, my opinion
is that if you have registered company.com for the internet DNS name,
then use corp.company.com for your domain name. It is easier to
manager the DNS resolution. You may take a look at the following
article also:


Enterprise Design for DNS
http://www.microsoft.com/technet/itsolutions/wssra/raguide/NetworkServices/i
gnsbp_2.mspx

b) I set up a brand new install of W2K3 server and ran DCPROMO, I
couldn't make the server to contact first AD.  I set up WINS on the
first AD and on the fresh W2K3, I added WINS address as well in the
LMHOST file, I have the DNS of the first AD.  From a DOS window, I
can ping first AD using DNS name.


I have the same opinion with Ace, this is the DNS srv record as I
have said in another newsgroup. However, I understand you are using
Unix DNS to serve win2k3 domain. Actually, it would be better and
easier if you have an AD integrated DNS in the network. The issue you
have encounter is because the client can find the DNS server,
however, the DNS server has not the srv record to let the client know
where is the domain controller. When the domain controller starts up,
it will automatically register the srv record in DNS server; the
client query DNS server to get srv record and then can locate to the
DC. Therefore, the Unix DNS should support srv record, dynamic update
and so on. If the Unix DNS version does not support these conditions,
you can create a win2k3 DNS integrated with the Unix DNS. Please take
a look at the article below, the concept is the same in win2k3 domain:

Integrating Your Active Directory Namespace Into an Existing DNS
Infrastructure With Name Overlap

http://www.microsoft.com/windows2000/techinfo/reskit/deploymentscenarios/sce
narios/dns04_integ_adnspace_with_nameoverlap.asp


there are some third-party websites address Unix DNS and windows, you
may be interested:
Windows 2003 Interoperability with unix DNS Servers
http://www.avidware.net/Linux/Windows-2003-linux-dns-server.asp

Integrating UNIX DNS with Windows 2000
http://emea.windowsitpro.com/Windows/Article/ArticleID/7874/7874.html

If you intend to use Unix DNS server does not support SRV, upgrading
Unix DNS is a easier way; otherwise, implement win2k3 DNS in the
network could be a little complicated task. You may consider
contacting Microsoft phone support engineer to smoothly implement the
DNS service in the network.

There are really many things to learn to be familiar with win2k3
domain. If you have any update or questions, please feel free to post
back.


Hi Rebecca,

I didn't realize the poster was using Bind for their DNS solution, as apparently you've found out seeing their post elsewhere.

And I agree with you, using a child name of the external corporate domain name presence (ad.externalDomainName.com), is a good solution for the start of the AD namespace and has no administrative overhead.

Ace 

.

Relevant Pages

  • Re: DNS and main domain controller is not working
    ... Is the branch office server also DNS server? ... i had additonal domain controller in other brach city. ... The query was for the SRV record for _ldap._tcp.dc._msdcs.sanad.itg ...
    (microsoft.public.windows.server.dns)
  • DNS Problem When Running DCPROMO
    ... dns problem. ... >resource record used to locate a domain controller ... with a DNS server ...
    (microsoft.public.windows.server.dns)
  • Re: Cant connect to domain
    ... Looks like the DNS server settings in IPCONFIG are wrong - they should be ... > - The DNS SRV record is not registered in DNS. ...
    (microsoft.public.windowsxp.network_web)
  • Re: In-place upgrade steps and concern...
    ... Are you saying NOT setup Child Subdomain DNS in AD? ... they are all pointing to Unix DNS server as Primary and secondary. ... > domain to host win2k3 domain FQDN resolution. ...
    (microsoft.public.windows.server.migration)
  • Newbie Questions
    ... Primary DNS server? ... >Server, DNS server, and Domain Controller. ... >- The DNS SRV record is not registered in DNS. ...
    (microsoft.public.windows.server.dns)