About DNS naming convention for Active Directory
- From: "Newbie" <newbie@xxxxxxxxxxx>
- Date: Mon, 6 Jun 2005 09:04:03 -0400
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
.
- Follow-Ups:
- RE: About DNS naming convention for Active Directory
- From: "Rebecca Chen [MSFT]"
- Re: About DNS naming convention for Active Directory
- From: Ace Fekay [MVP]
- RE: About DNS naming convention for Active Directory
- Prev by Date: Re: Dcdiag error
- Next by Date: Re: update of zone file manually using dnscmd /zonereload - locked after update
- Previous by thread: Dcdiag error
- Next by thread: Re: About DNS naming convention for Active Directory
- Index(es):
Relevant Pages
|