Join a Domain?

raoul_1101

raoul_1101

Member
Hello,

I'm trying to create a domain I can play around in on my Server 2008 machine. But, I hit my first snag early on. Naming my domain- I have to name it a Fully Qualified Domain Name (FQDN) so other computers joining can find it. I tried making a dummy domain- dummy.test - to see if another computer could join it, but it couldn't find it, the DNS server had no idea where dummy.test was. Anyone with knowledge on setting up a domain, it would be greatly appreciated.

Thanks!
 
when you added active directory to the server you would have added dns at the same time or at least you should have.


your server should have a static ip address pointing to itself as the dns server

other clients should be on the same network with the DNS pointing to the server.
 
I did install DNS. Another thing I'll add though, I'm not the administrator of this network, so I have dynamic IP addresses, and if I changed that I would lose connection.

Although, just for testing purposes I'll try giving it a static IP to see if it will work. Thanks a bunch!

Will the DNS of the server automatically know that dummy.test is itself? Or would I have to add it to a text file somewhere?
 
the machine that hosts dummy.test will be configured to be the domain controller so this needs to be a static IP. with the IP address in the DNS section aswell.

its also set to resolve local DNS for the domain of dummy.test all clients need to have the IP address of the domain controller within the DNS section of internet properties.


if your not the administrator of the network get permission as your going to cause problems on the network.



you could set up a small virtual network using virtual pc or vm ware.
that could be done without affecting the network
 
You need to do the following:

1) Run the DNS service and configure your server with a static IP and FQDN

2) Name your AD server in conjunction with what is in your DNS

3) not required, but running DHCP from the server can also dish out DNS servers as well

4) BIND client to AD controller by FQDN
 
You must log in or register to reply here.
Back
Top