Domain name conflict

[jallen]

My predecessor upgraded our NT4 domain of "company" to W2K
AD. We had 2 domains: "company", which is our internal
office domain, and "companysource.com", which is our
external web presence. We use DJBDNS for our name
resolution, and this can't be changed. Since before my
arrival, all of our clients and servers have had the DNS
suffix of "companysource.com" added to their TCP/IP
properties. When looking at the computer name for our DC's
in the "company" domain, they show themselves
as "W2KAD01.companysource.com" and
W2KDC02.companysource.com". Now I'm running into problems
establishing a trust between the two domains, along with
various other problems. When view ADUC in either
domain, "companysource.com" is the name that shows at the
top level. The Unix DNS admin has delegated authority for
the _tcp, _udp, _msdcs, and _sites zones to a new W2K DNS
zone that I established, companyAD.companysource.com. I
can reset the connection-specific DNS suffix to this name,
but how can I set the primary DNS suffix of my DC's to
this name without A)wreaking havoc B)demoting/promoting C)
disrupting business? I'll be glad to send specific info to
an email address for help. Thanks in advance!

 

[Ace Fekay [MVP]]

In

My predecessor upgraded our NT4 domain of "company" to W2K
AD. We had 2 domains: "company", which is our internal
office domain, and "companysource.com", which is our
external web presence. We use DJBDNS for our name
resolution, and this can't be changed. Since before my
arrival, all of our clients and servers have had the DNS
suffix of "companysource.com" added to their TCP/IP
properties. When looking at the computer name for our DC's
in the "company" domain, they show themselves
as "W2KAD01.companysource.com" and
W2KDC02.companysource.com". Now I'm running into problems
establishing a trust between the two domains, along with
various other problems. When view ADUC in either
domain, "companysource.com" is the name that shows at the
top level. The Unix DNS admin has delegated authority for
the _tcp, _udp, _msdcs, and _sites zones to a new W2K DNS
zone that I established, companyAD.companysource.com. I
can reset the connection-specific DNS suffix to this name,
but how can I set the primary DNS suffix of my DC's to
this name without A)wreaking havoc B)demoting/promoting C)
disrupting business? I'll be glad to send specific info to
an email address for help. Thanks in advance!

Send me an email. Use my actual first and last name at hotmial.

I have a script that will set the Primary DNS Suffix to the AD name,
provided the AD name is the correct domain name.

Also, just to point out, when creating a trust between two domains, (of
course of different forests), it is NOT DNS based, but rather NTLM/NetBIOS
based, so you would need NetBIOS name resolution support, such as WINS or
static name mapping using an LMHOSTS file.

If they are of the same forest, then a trust is created by default.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory