15 replies
To install Win2k with AD, if you do not have an existing DNS server, then during the installation, you will be required to make the Domain Controller a DNS server. Active Directory requires DNS to operate. Without DNS, then you will not be able to install AD.
Hope this helps.
by digerati
My problem is that the server was installed with AD, it is the only server in the domain, and there is no DNS for AD to link too. I do not understand how the user acounts or security even work as I thought it had to have a functional DNS (automatic update or static update). So my question is.. What are the affects of not having the DNS? The server seems to be running ok and users can login and map drives and access files. So what are some symptoms of problems that I should see given this situation?
Your Win2K server with AD is a DNS server too, even if you have never configured it. Active Directory will not work correctly until you configure the DNS server. Service Resource Records will not be available, so clients can only query for a particular server by name, not by service. Also there will be no dynamic updates on your Win2K clients without a properly configured DNS.
http://www.microsoft.com/windows2000/techinfo/reskit/deploymentscenarios/scenarios/dns_02_sir.asp
by digerati
Poster rated this answer.
I have a question. Your server, is it a network server, or did you run DCPROMO to promote it to a Domain Controller? If you did Not run DCPROMO, then you do not have Active Directory installed, and therefore may not have DNS.
If you have (or someone else) run DCPROMO, then DNS will be installed on that server, since you state it is the only server on the network. To check, click on Start \ Programs \ Administrative Tools. You should find a menu option for DNS. Click on it. When it opens, you should find your server name in the left-hand windows. When you click on it, it should expand and you will find 'forward look up zones' and 'reverse look up zones'. Expand these and you will find the DNS name of your LAN. When you then click on it, it will expand and you must find the following 4 sub zones. _msdcs, _sites, _tcp, _udp. If they are there, then DNS and AD is installed. If they are not there, then you do not have Active Directory installed.
If DNS is installed, it will only be configured for the LAN (local area network). Each of your workstations will need to have their DNS settings for two DNS servers. The first one should be the IP address of your server, the second one the IP address for your ISP. If your ISP gave you a second DNS IP, then add that one as your third one for each workstation.
If you have other questions, ask and we will try to help out.
Best of luck.
by digerati
by joseph moore
You have gotten some good answers for this one. I think you are being pointed in the right direction.
Now,I have a question for you. Did you do the AD install yourself, or is this a server you inherited?
If you did the AD install (running DCPROMO), then did you select to have DNS be installed during the AD process, or did you select the "install DNS later" option?
If you did NOT install AD on this server, then when you go to view user accounts, are you using "AD Users & Computers" snap-in???
There is just a lot of confusion here. I just want to clear up for sure if AD is running on the server or not.
by joseph moore
Next, it would be theoretically possible to run AD without DNS. There would just be a lot of NetBIOS B-type record broadcast going on as clients try to find out what machine is their domain controller.
You see, Win2K, XP and 2K3 all use DNS as their primary method for finding their domain controllers, but it is not the only way. All of the newer Windows OS's will eventually fall down to quering a configured WINS server or just doing NetBIOS broadcast to find out who should authenticate them, and where the server is to map drives and print to shared printers and such.
So, if you do have AD running without DNS installed, then it would be possible for clients to still work.
It is weird, doing this way! But possible.
by digerati
Yes this is an inherited server, AD is installed and you have to use the AD users and computer plug-in. I am assuming that the install dns later option was used as well. I finally got a hold of the installer and he says that's the way I always do it and i never have any problems.
I am assuming that even though this is a small network (10seats) this would account for slow response on the network as there is no dns resolution and it takes time for the computer to time out dns queries and resort to NetBIOS. So other that not being able to add another server to the domain, are there any other strange and wonderful things that could be affected in this scenario?
by ewgny
by digerati
Actually this is the full version, but thanks anway
by bournese
by digerati
by digerati
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending