domain.local for Windows 2003 Active Directory

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I installed a new Windows 2003 server(named SV1) as a domain controller with Active Directory. An internal domain name was used "Burbank.local" instead of the public domain name(Burbank.com). DNS service was also installed on the server and the server itself was configured as a primary DNS server. After that I tried to install a second Windows 2003 server(named SV2). However, it could not find the the first domain controller. On the SV2, I could ping SV1 successfully. However, I failed to ping either SV1.Burbank or SV1.Brubank.local . As I open the DNS service on SV1, I saw only the" _msdcs" folder instead of the four of "_msdcs, _sites, _tcp, and _udp" folders. Is it normal for the domain.local type of internal domain name configuration? I'm frustrated why I cannot ping to the full computer name with domain name suffix. Actually, I don't know the computer name suffix supposed to be SV1.Burbank or SV1.Burbank.local . Please help!
 
I recommend to make the zone active directory integrated if it´s primary,
TCP/IP DNS Settings have to be set to this the server running dns on the
addinational server you try to promote.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup
------------------------------------------------
http://www.chrisse.se - Active Directory Tips

sang said:
I installed a new Windows 2003 server(named SV1) as a domain controller
Click to expand...
with Active Directory. An internal domain name was used "Burbank.local"
instead of the public domain name(Burbank.com). DNS service was also
installed on the server and the server itself was configured as a primary
DNS server. After that I tried to install a second Windows 2003
server(named SV2). However, it could not find the the first domain
controller. On the SV2, I could ping SV1 successfully. However, I failed
to ping either SV1.Burbank or SV1.Brubank.local . As I open the DNS
service on SV1, I saw only the" _msdcs" folder instead of the four of
"_msdcs, _sites, _tcp, and _udp" folders. Is it normal for the
domain.local type of internal domain name configuration? I'm frustrated
why I cannot ping to the full computer name with domain name suffix.
Actually, I don't know the computer name suffix supposed to be SV1.Burbank
or SV1.Burbank.local . Please help!
 
Hi there sang,


First Review the following articles:

300202 How To Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202

317590 HOW TO: Configure DNS Dynamic Update in Windows 2000
http://support.microsoft.com/?id=317590

817470 HOW TO: Reconfigure an _msdcs Subdomain to a Forest-wide DNS
Application
http://support.microsoft.com/?id=817470

816101 HOWTO: Convert DNS Primary Server to Active Directory Integrated
http://support.microsoft.com/?id=816101

If you are in or have a Child domain please review this article:
300202 How To Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202


Well, if you want to promote a second domain controller I always recommend
that the server be joined to the domain as a member server.

1. When you do this Make sure that the Primary DNS server IP Address in
the Network card configuration points to the IP Address of the First Domain
Controller. If you have already installed DNS on the server you are trying
to promote, then add as the Alternate DNS Server the new servers IP Address.

2. When Joining the server to the domain, make sure you use the FQDN of
the domain: ie burbank.local.

3. Once you have joined the computer to the domain you will need to reboot
the server.

4. Then logon as a Domain Administrator once it comes backup.

5. Run the DCPromo Process to promo the server to the domain.

6. Once the New domain controller is promoted and rebooted, you may want
to add its IP Address in the Alternate DNS Server settings of the Network
card on the First Domain Controller.

I hope this helps!

Best regards:

(e-mail address removed)

This posting is provided "AS IS"
with no warranties, and confers no rights
 
Back
Top