DNS / Trust isue

  • Thread starter Thread starter Strunk
  • Start date Start date
S

Strunk

Hello,

Enviroment: 2 networks connected through VPN. Both networks are Windows 2003
based
on AD.

I have a problem that it thing might be solved with the right use of DNS. I
want to setup a
trust between the two AD's but everytime a write the domain name in the
Trust wizard is
says that it its not a valid domain name an.

The remote domain is called remote.com and my local is called local.com. I
can't resolve
remote.com through my DNS only anyname.remote.com.

Now it might be me that is doing something wrong here but i write remote.com
in the Trust-Wizard
i have also tried with domaincontroller.remote.com which is the Global
catalog server at the remote
site (which can be resolved through my DNS) but nothing works.

What i'm i doing wrong here - is it my DNS or have i misunderstod the name i
have to write in the
Trust-Wizard ????

TIA,
Strunk
 
Strunk said:
Hello,

Enviroment: 2 networks connected through VPN. Both networks are Windows
2003 based
on AD.

I have a problem that it thing might be solved with the right use of
DNS. I want to setup a
trust between the two AD's but everytime a write the domain name in the
Trust wizard is
says that it its not a valid domain name an.

The remote domain is called remote.com and my local is called local.com.
I can't resolve
remote.com through my DNS only anyname.remote.com.

Now it might be me that is doing something wrong here but i write
remote.com in the Trust-Wizard
i have also tried with domaincontroller.remote.com which is the Global
catalog server at the remote
site (which can be resolved through my DNS) but nothing works.

What i'm i doing wrong here - is it my DNS or have i misunderstod the
name i have to write in the
Trust-Wizard ????

TIA,
Strunk
It is likely a DNS issue. Try setting up secondaries in each domain's
DNS for the other domain.

....kurt
 
Strunk said:
Hello,

Enviroment: 2 networks connected through VPN. Both networks are
Windows 2003 based
on AD.

I have a problem that it thing might be solved with the right use of
DNS. I want to setup a
trust between the two AD's but everytime a write the domain name in
the Trust wizard is
says that it its not a valid domain name an.

The remote domain is called remote.com and my local is called
local.com. I can't resolve
remote.com through my DNS only anyname.remote.com.

Now it might be me that is doing something wrong here but i write
remote.com in the Trust-Wizard
i have also tried with domaincontroller.remote.com which is the Global
catalog server at the remote
site (which can be resolved through my DNS) but nothing works.

What i'm i doing wrong here - is it my DNS or have i misunderstod the
name i have to write in the
Trust-Wizard ????

On the local DNS server properties sheet, select the Forwarders tab under
DNS Domain, click "New" enter the Domain Name of the trusted domain, click
OK, check the "Do not use recursion for this domain" box and enter the IP
addresses of the DNS server for the other domain.
If both are Win2k3 you can do this on both DNS servers. It is important to
check the Do not use recursion box to prevent the DNS server from trying to
go to the root to resolve a Private domain.

-
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
Send IM: http://www.icq.com/people/webmsg.php?to=296095728
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
 
Back
Top