RE: About DNS naming convention for Active Directory

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.

Good luck!

--------------------
>From: "Newbie" <newbie@xxxxxxxxxxx>
>Subject: About DNS naming convention for Active Directory
>Date: Mon, 6 Jun 2005 09:04:03 -0400
>Lines: 30
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
>X-RFC2646: Format=Flowed; Original
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
>Message-ID: <eOVo4gpaFHA.3328@xxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.dns
>NNTP-Posting-Host: gw1.gennum.com 209.47.33.228
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.dns:12450
>X-Tomcat-NG: microsoft.public.windows.server.dns
>
>Below is the email I posted on windows.server.active_directory newsgroup
and
>someone suggested to re-post here as it's related to DNS issues.
>
>------------------------------------
>
>Hi,
>
>I've successfully upgraded a NT4 PDC to Windows 2003 Active Directory
>running interm mode. Clients can connect to AD no problem. I configured
>without setting up AD as DNS server.
>
>I have a few 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.
>
>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.
>
>Thanks,
>
>Simon
>
>
>

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA


Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

.

Relevant Pages

  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... AD-Integrated DNS does not do zone transfers between the ... your DNS server will bypass ...
    (microsoft.public.windows.server.active_directory)
  • Re: Servers hang on boot
    ... The last DC at that site (not a DNS server). ... EventID: 0x00000457 ... (Event String could not be retrieved) ...
    (microsoft.public.windows.server.networking)
  • Re: DNS Redesign Issue
    ... set the new child domain DNS server as primary for the domain controllers? ... -If you are going to create a new AD Integrated Zone in each child domain, ...
    (microsoft.public.windows.server.dns)
  • Re: Internet connection wizard
    ... turn on DHCP on the workstation. ... Connection-specific DNS Suffix. ... calling CNetCommit::ValidateRouterConnectionProperties. ... Call to Reading preferred DNS server IP returned ok. ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC Endpoint Mapper Error
    ... Event Type: Warning ... I checked DNS entries with articles from Microsoft on ... PASS - All the DNS entries for DC are registered on DNS server ... List of NetBt transports currently bound to the Redir ...
    (microsoft.public.win2000.active_directory)