Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Install Active Directory - does it require a sufix name?

Status
Not open for further replies.

ljCharlie

IS-IT--Management
Joined
Apr 21, 2003
Messages
397
Location
US
When I install my domain controller, do my domain name has to have a "dot" something? For example, can I have something like MyDomain instead of MyDomain.Local or some other sufix? One other question, do I have to have a static IP address? What if I received a static IP address from my ISP already, do I then choose the "Obtain an IP address automatically" option on Internet Protocol properties or do I have to put in the static IP address manually by selecting the option "Use the following IP addresse:"?

ljCharlie
 
Domain controllers should have a static IP address.

In Windows 2000 and higher, DNS is required for the domain to function properly. Therefore, it is necessary to use the "."

Microsoft.local, for example, is the fully qualified domain name. However, the netbios name of this domain is just microsoft.

-hope this helps.

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
 
Many thanks for your help. The reason I asked is because I just want a domain controller so my client computers and logon to it. I don't installd the DHCP server. All of my client computers including the domain controller received their static IP address from the head quarter DHCP server. Now, with this said. I'm pretty sure that I need to install DNS server on my domain controller; however, I'm not sure how to configure my Internet Protocol (TCP/IP) properties. Do I leave it dynamically obtained or manualy configured the ip address and dns to point to the head quarter's domain server or pointing back to mine domain controller? Which one should I configure it to?

As for the namespace, I'm pretty much have to have something after the domain name, correct? I tried .local and it seems like my client computer cannot connect to it because again, all the ip address are coming from the head quarter domain server and I configured my domain server to be a forest domain server as well. That is why I like to know if I have to put .local or something else at the end of the domain name.

ljCharlie
 
The local server that you are building must have DNS installed for it to work as a domain controller (yes, you must have a ".somthing" .local, .com, .org, .msft, .net, etc)

You seem to be building a new domain controller for a NEW domain. And it doesn't seem like you want this domain controller to be serving the existing domain....that you are creating a new domain.

With that said, you need to point the local TCP/IP properties of the new domain controller to point DNS to itself (not to the current DNS server).

In order for your clients to join the NEW domain, you must make sure that they have an IP address that is using your NEW DNS server only. In other words, the clients must not use the existing DNS server. The clients that you want to participate in your new domain must use the DNS server of your NEW domain.

However, the clients will not be able to join more then one domain at a time. Meaning if they join your new domain, they will no longer be a part of the old domain.


If you want clients to be able to use resources on BOTH domains (existing and new), you should create a TRUST relationship between the domains...


-hope this helps..

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
 
It clears up my confusion a bit. Okay, see if I understand this correctly. I will have to point all of my client computers' DNS to my domain server's dns server, correct? At the same time, all of my client computers still can receive their IP address from the original domain server, correct?

ljCharlie
 
Again, many thanks for your help. I understand it now. However, if you don't mind and still have some time, will you take a look at this thread "Can not find domain users on domain server"? I have the server and client computer setup as you have suggested but I coldn't figure out why the client computer can't see the domain server. I want to add some domain users to be able to access the client computer remotely via Remote Desktop Connection, but like I said, the domain server wasn't listed.

Anyway, if you have time please take a look. I really need help on it.

Thank you so much!

ljCharlie
 
Never mind, it works! I just have to reboot my client computer. Thank you so much! You are so wonderful! I have been trying to figure this out for a week now. I guess pointing the client's dns to my domain server's dns server is really the solution.

ljCharlie
 
Active Directory clients require DNS to communicate with the domain.

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top