New 2003 server/ad/dc not seem

After a quick install, I can't join the new domain I just created. Have existing 2k server domain and the new domain uses the xxx.local naming. When I try to join it from the first computer I get domain "xxx.local could not be contacted" DNS SRV record not registered. I haven't kept up with all this stuff, and my primo RDBMS skills are not helping here. HELP!

edit-
The netdiag tool shows under

netBT name: not a single interface with the Workstation Service/ Messenger Service/ WINS names defines

DNS: cannot find a primary authoritative DNS server for the name machine.domain.local when I run it on the new server.


-Thanks Glenn

FYI: DHCP is through GW/FW (not other Server) and I can ping it just fine.
Disabled routing/vpn service (was causing ping to fail so I thought this was bad - and I was not using it)
DNS for NIC on new machine points to loopback 127.0.0.1 (what should this be?)
DNS service on new server just have forward lookup zones (I don't know how to set these either) for the a few names (all server.domain.local stuff)

 

Hi, it sounds like your problem is very typical of name resolution issues. In order for a machine to join an Active directory domain, it has to locate service records in DNS. Here is the simplest way I know how to get you on your feet. On your domain controller, install DNS. Create a zone in DNS that represents the name of your AD domain. For example, if my AD domain name was sugarsmacks.com then I would create a zone called sugarsmacks.com. - Create it as an Active Directory integrated zone. Right click on the zone, go to properties, and then enable dynamic updates. Then on your domain controller, go to a command prompt and type: "netstop netlogon" --- please type without the quotes. then press enter. Then type "netstart netlogon" and press enter.

in your DNS management console, you should see a bunch of stuff like _msdcs, _Sites, _tcp, _upd get created - and you may have to press F5. once that is done, on your client that you are trying to join to the domain, on the TCP/IP properties, make sure you put in the ip address of your domain controller as your DNS server.

------PLEASE NOTE --------> this does not necessarily constitute best practices or anything else for a production AD domain environment. I have no idea how the rest of your domain is setup and you should probably review some AD design docs or have someone with AD design experience work with you to make sure you have a good and stable DNS and AD environment.

My best,

Desiree

 

Still confused

I have two books upon and a browser on the DNS help and the DNS console up and I am unable to figure this out. So maybe if I outline this for you you could at least point me in some better direction.

I have a two working domains called BWMA and BWMB. They are connected by a sonicwall router/vpn setup over t1's and trust each other.

They both use the sonicwalls as dhcp servers. I am replacing both domains with a new domain BWM. The new domain needs to come up, then the BWMA users will migrate, then the BWMB users will migrate and I will take both of those server groups off-line. I understand the basic DNS ideas but I don't get how the DHCP configures the DNS settings on my workstations and how having multiple domains and DNS servers effects the host lookups. The new domain is running on one adv svr 2003 r2 x62 box and I can run DHCP on it instead of the sonicwall if that is what I should do. So..

Where do I run DHCP for best practices? On the router or DC box? How do I configure the DHCP while both (all three) domains are up? How do I set DNS so that I can see all the servers on the untrusted domains?

When do the DNS entries get set on the client? Because my workstation lists three dns servers, the first two are from the ISP the last is the address of the older ws2k server that I log into on the older domain (192.168.1.2). Where does list last address come from beacuse the DHCP server (sonicwall) does not have it explicitly set.

Also why does the new server (BWM) have a single DNS listed as 127.0.0.1?
What does that do by pointing to itself? I don't even see the ISP DNS entries anywhere... how does it know where to fwd external requests to?

The ip scheme is simple: lan 1 uses 192.168.1.x lan 2 uses 192.168.0.x and the sonicwalls fwd everythings between these two ranges.

I wish the DNS and DHCP chapters were more clearly written in all the books and online help. The ideas are clear but the implementation steps are either "click this on" or some convoluted list of examples for massive networks.

So I should go back to DB work, right? Right now I am prepping this place for a major SBS/SQL/SERVER software upgrade. So I can't wait.

Thanks.
Glenn

 

Quick Question: are BWMA and BWMB Active Directory domains?

Thanks

Desiree

 

Everything is AD

Both domains (BWMA and BWMB) are active dir under ws2k. There are 3 phys servers for each domain (a pdc and bdc and dns running at each location).
I really just want to understand how to use dhcp properly to get the dns clients entries set corretly.

BTW, thanks. I simply added the DNS entry for my new server (BWM) to the nic setup and voila! it found the new server. I joined the new doamin and I was able to start testing the AD configuration. So I felt better.

Glenn

 

OK, personally, here is how I would do it since you have to worry about 3 domains now.

LocationA:
DC(s) for BWMA

IP configuration - point to LocationA BWM DC for DNS​

DC for BWM - running DNS and DHCP

DNS, create zone for BWMA, BWMB and BWM, enable dynamic updates, ACTIVE DIRECTORY INTEGRATE THE ZONES - this will make it so that this data replicates to both BWM DC servers​

IP configuration, point to LocationB BWM DC for DNS or itself if you havent spun up that domain controller yet. when you spin up LocationB BWM DC, on initial DCpromo, have it point to LocationA BWM DC for DNS until it is finished replicating, etc and then modify the DNS settings so that they each point to each other for DNS​

DHCP Scope, Scope option for DNS, hand out BWM DC IP address​

LocationB:
DC(s) for BWMB

IP Configuration - Point to LocationB BWM DC for DNS​

DC for BWM - running DNS and DHCP

IP Configuration, point to LocationA BWM DC for DNS​

Verify that AD recplication is happening between both locations - the big thing to remember is that you don't want to create the DNS Island effect​

DHCP Scope, Scope option for DNS, hand out BWM DC IP address​

I would also recommend that each BWM DC\DNS server be a Global Catalog Server and that each server uses forwarders to forward external DNS requests to your ISP.

My best,

Desiree