Re: DCPROMO from a workgroup computer
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Tue, 28 Nov 2006 00:37:13 -0000
Hi
You need to know how DNS and AD Domains works, after that all you need to create a new domain tree is to follow the link.
There're many MS articles to DNS best practices in different scenarios, so before you start creating domains, you must know what you're doing, and of course I can give you some tips about specific configs but I'm not going through detailed process, please look at MS for documentation then after you understand it correctly try to create your new domain, if you have problems post here.
Dns basics are:
Assuming DNS AD Integrated Zone
-Make sure that each DNS server points to itself under NIC preferred DNS. If the Server IP-Address is 192.168.0.1 then the preferred DNS should also be 192.168.0.1.
-When Adding Additional DCs to an existent Domain, and if you want to make it a DNS server, Install DNS service, make sure that the server (the additional DC) points to the existent DNS DC under NIC preferred DNS, then run Dcpromo, wait or force replication (this can take a awhile), then check on DNS console, and if the DNS zone is already transferred, then point the additional DC to itself again.
- Clients: Make sure that the clients only use their local available DNS server(s) on their NIC DNS configuration. Do not place the ISP DNS server or any other DNS on the client or DNS Server NIC properties, this is a common mistake. The clients should use their local DNS server to resolve all queries. It's up to the local DNS server to handle the Internet resolution as any other Zone that the DNS is not authoritative for. Check the link for configuring DNS for Internet resolution.
Note: The DNS client does not utilize each of the DNS servers listed in TCP/IP configuration for each query. By default, on startup the DNS client will attempt to utilize the server in the Preferred DNS server entry. If this server FAILS to respond for any reason, the DNS client will switch to the server listed in the alternate DNS server entry. The DNS client will continue to use this alternate DNS server.
Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/kb/825036/en-us
How to configure DNS for Internet access in Windows Server 2003
http://support.microsoft.com/kb/323380/
You can look for more info at MS site
GOOD LUCK
--
*************************************************
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA + Exchange + MSCE
*************************************************
"Gaetan" <me@xxxxxxxxxxxxx> wrote in message news:99umm2l2mimlcs6sh7si7pgm2tr649q5dt@xxxxxxxxxx
Thanks Jorge,
I'm slowly assimilating the information from the links you provided. So far, no light bulb went off.
I also tried to make the new DC a mamber of a domain prior to the DCPROMO process ... still same
result as from a workgroup computer. I'm following this post in a new post I made (preparing network
connections ... forever) since I now get a lot fewer DNS/AD error/warning but I'm still not in the
home stretch.
G.
.
- References:
- DCPROMO from a workgroup computer
- From: Gaetan
- Re: DCPROMO from a workgroup computer
- From: Jorge Silva
- Re: DCPROMO from a workgroup computer
- From: Gaetan
- DCPROMO from a workgroup computer
- Prev by Date: Re: Preparing Network Connections... forever
- Next by Date: Re: Preparing Network Connections... forever
- Previous by thread: Re: DCPROMO from a workgroup computer
- Next by thread: LDAP work on my Server but not on LOCAL, why ?
- Index(es):
Relevant Pages
|
Loading
