Help with DNS setup

Is this the first server in the forest?
In a new child domain of the forest?
Or just another dc in a domain?
Depending on the answer, this will vary how you set up DNS once the DCPROMO process finished.

My advice is to let DCPROMO handle it for you.

Either will work but letting DCPROMO wizard do it is
easier.

As before, use a private ip as you are and a private
namespace ".local".

be the only domain in the forest and you are NOT a root
domain. If you choose root domain then go to DNS and
delete the "." zone.

Good luck again.

razz

I've been following your threads, seeing the suggestions and wonder if you got your problem solved?

I will say this, on W2K and W2003 using the wizards to initially setup a single DC to provide DNS, DHCP, AD services in a single domain pretty much goes smoothly. Note that during rebooting after configuration changes, that you'll see errors pop up in the event viewer. Some are related to the service order startup, some are bugs and SPs and Hotfixes will fix these. You shouldn't get overly excited about errors poping up in the Event Viewer until you have configured the server, installed all the critical and some of the recommended service packs and hotfixes, reboot the bugger and let it run 24hrs or so. [why we use a test network before placing servers into a production environment].

Your comment used to have a standard answer. It was
anytime you install new components from a source CD
you always re-apply the service pack anyway. This was
common in NT but less in 2000 and 20003 due to the
protections added to prevent an added feature from
overwriting a newer system file. Many still do practice
that.

Now the other concept. Service packs add patches,
fixes, features and yes bugs. The new features is
always my focus. I feel it is better to update to SP4 and
then do DCPROMO with the latest components
installed. Then it is not required for you to redo SP4
again, but you may choose to. Having SP4 when you
DCPromo though does allow for newer system
components to funtion and prevent any bugs they were
designed to fix.

razz

I can't get a station to join. http://www.microsoft.com/windows2000/dns/tshoot/dns_tshoot2A.asp
I checked evrything in this article and tried the flushdns and registerdns and still nothing.
my domain is ctc.local and I have all the right stuff in DNS I think. What are the tools or commands to see what is holding me up.
on the WS I am trying to join the domain and instantly I get the error. On the DC when I go to the Network tab the properties box is dimmed.

heres what I do. I install W2k server. set a static ip address for the NIC and run windows update and get ALL of em. Once they are all installed, I run the DNS wizard to install DNS. Since the NIC already has an IP address assigned [and I've chosen the IP address to be the range I want for the network] the Wizard uses it [I use the first # in the last byte for the IP address e.g. if I want the network to be 192.168.4.1-254 the DNS server is 192.168.4.1]. I use the .network for my internal name. Windows will want to build a LAT and install class A,B,C addresses and I remove all except that which I will use on my LAN.

Once DNS is installed, I install DHCP and use the wizard. I authorize the scope and activate it.

Once I have DNS and DHCP installed I review DNS and perform some lookup queries in DNS to make sure I've got resolution. Right click and open your DNS in the left pane and run the DNS query. You could do a recursive IF you have an internet connection active but not necessary for LAN DNS resolution.

Once all that is done I install Active Directory and use the Wizard. I do not use dcpromo from the command line. [lazy]. Easier to just click the link in the setup page.

I have found in my DNS there are no subfolders with
_MSDCS
_SITES
_TCP
_UDP
There are just three text files which are the
SOA
NA and
A record
What should I do now? Can I fix this with out re-installing again?

Point value changed by question poster.

Ok I did the registry edit and it seems to work. How can I test DNS to make sure it is working?

nope you don't install DHCP first, you install DNS first. DHCP is only for assigning IP addreses to client computers and to provide those client computers with connectivity information like default gateways, DNS servers, WINS servers. You assign a static IP address to the NIC on the server using the Class and range you want your local network to use. After that, you can, as an option, install DHCP. DHCP is NOT required for an Windows Active Directory based network. It just makes it easier assigning IP addresses to clients, adding records to DNS for clients, providing clients with default gateway addresses and whatnot. you can always ADD DHCP services at a later date.

If you have a SOA, Host and A records in DNS. Then you've got the basics necessary for name to IP address resolution.

The DNS server properties has built-in tests, but also
the one I like is to add an A record or C record and
have it some weird name like test.btb.local pointing to
an existing ip. The try to ping it by name. it should work.
(Restart DNS if you want first but you don't need to.)
You can also ping the ip and it should show the DNS
name.

razz

I did a nslookup and seems to be working. I went to do a DCpromo and it says the wizard cannot contact the DNS server that handles the name CTC.local to determine if it supports dynamic update. confirm your DNS configuration, or install and configure a DNS server on this computer.
What do I do to see what could be wrong with my DNS?

Hate to be harsh but,from all all your questions that keep getting more and more complicated and more and more problems arise that under normal installations do not appear, you either no absolutly nothing about setting up DNS, in which case you really need to take a course or read a book on DNS in a Windows based system or, you just keep making the problem more complicated to see who knows the most about Windows DNS.

DNS has a management properties. If you right click on your server, choose properties, on the properties page you'll see a portion for updating. you can choose how you want DNS to update their records and what computers/servers will be allowed to provide updates to DNS.

Get a Windows Server [whatever flavor] self paced training book. Read it, do the practice labs which walks you through setting up your DNS server, DHCP server, WINS, and Active Directory step by step.

yeah right

dog and pony show

OK, I have been out for a few days and this has gotten funny.

"I tried going to the network tab and entering in my domain
name as CTC.local and it comes back with an error just like this:
http://www.microsoft.com/windows2000/dns/tshoot/
dns_tshoot2A.asp
I look at the registry edit and don't know if I should try it. I have
not installed AD yet. the only entry I don't have for regedit is NV
Domain. I might try the registry edit.
I don't want to install AD yet till I get my Domain Straight."

How could try to join a domain (AD Domain of BTB.local) if you
have not created it yet? How can a domain be 'straight' if you
have not done the AD part? Of course the domain records do not
exist if it (the domain) does not exist. JUST LET THE DCPROMO
WIZARD DO IT ALL INCLUDING DNS.

I want you feel that feeling of success so here we go:

Start from a fresh install. Upgrade all patches and SP's. Choose
Start menu and run then type "dcpropmo in the box. (without
the quotes) follow the wizard. The following links are step by
step guides. Print them out to have them handy.

http://www.petri.co.il/
how_to_install_active_directory_on_w2k.htm

(sorry about the text wrap)

That guide has you install DNS first. For you I would skip that
and have DCPROMO do it.

MCP Magazine has a good tutorial too and it uses the wizard
DNS setup.

http://www.mcpmag.com/columns/article.asp?EditorialsID=141

Again, if DNS installs as a root then go to DNS and remove the
"." zone. Also set DNS to accept dynamic updates and if you
want to be AD integrated.

Be aware that some errors you may recieve are NORMAL and
according the great creator of all that errors "Mircosoft', can be
ignored. Some may be service start order, or another issue of
misconfiguration that did not show up until you ran AD and
DNS.

I wish you good luck,

razz

Well I am glad all is ok with the DNS now but i am confused. I am
I correct that the DNS issue for this question is solved?

As to the workstation issue, that would require info on OS and
login etc. and may be better suited as a new question. But, as
long as we are here...

Are you loging in at the workstation using a domain user
account or local user. Are you logging into the domain or local
machine? (When you hit ctrl-alt-del there should be 3 boxes,
name, password, and third should show local or domain. It will
not change to domain on it's own after joining.)

If you choose "run" can you access the share by typeing a UNC
path such as:

\\\

*** Note that it is share name and not folder name if they are
different.

Can you from the workstation DOS propmt do a 'net view'and
see resources?

net view \\

Are you sure the WS has joined the doamin and is listed in AD
under computers?

What are the share permissions and the NTFS permissions if you
are using NTFS?

razz

If you view the server shares using Net View, and can
open them using UNC then you are fine. If you cannot
see them in Network Place then the Master Browse List
is not up to date which is normal and can take aprox an
hour to sync up. To see them in AD they must be
shared and then published in AD.

razz

humm on to seeing shares on a workstation. Ok, administrative shares are appended with a $ to hide em. Unless you create network shares and publish them in active directory, you wont see any in my network places or if you browse AD no shares will show up [sans the sysvol folder]. Just create a shared folder and publish it to AD [during the creation process the wizard will ask you if you want to publish the share to AD, choose yes].

This question was closed by the author