Below is the error message when attempting to join domain.  It finds the DC.
nslookup can resolve the DC both forward and backward, so it seems that the
A record for DC must be right.

Now, here is the odd situation.  This W2000 DC (Domain1) is using another
server W2003 DC (Domain2) for it's DNS and the LAN's DHCP services.  (I
think this was done so the LAN would have a single DHCP server.)

I would even be willing to move the W2000 DNS services to reside on the
Domain1 DC if that would solve problem.  I'm not sure how to get all the DNS
records set up for Active Directory if not done as part of the original
dcpromo.

Any further advice appreciated. Russell

-----
DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain ccs:
The query was for the SRV record for _ldap._tcp.dc._msdcs.ccs
The following domain controllers were identified by the query:
ccsserver.ccs

Common causes of this error include:
- Host (A) records that map the name of the domain controller to its IP
addresses are missing or contain incorrect addresses.
- Domain controllers registered in DNS are not connected to the network or
are not running.
For information about correcting this problem, click Help.
    Search the Web:
     domain name

Hi Ace, Many thanks!!!!!

the article you referred to below solved my problem which was related to
having a single label window domain dns name.  The registery changes
corrected this difficult to resolve problem.  Russell

Hi Hank,

If he hasn't edited the error messages, I *believe* his problem may be there
is no TLD (such as ".local") on his domain name, which makes it a single
lable name, so he wouldn't be able to do that.

I think you got lucky your customer's DNS domain name was correctly created
at inception. I think the problem not being able to join using HOSPICS
NetBIOS name may indicate a lack of NetBIOS name resolution issue across
subnets. WINS would be answer for that, especially if all the DCs are at
their primary site.

Ace