Internal vs External Domains

  • Thread starter Thread starter XXXXXXXXXXX
  • Start date Start date
X

XXXXXXXXXXX

Hi Everyone:

I am planning an Windows 2003 Active Directory domain for a client company.
The external domain name, for example, MYDOMAIN.com is registered and has an
active website on the Internet. The internal domain name under AD is
inside.MYDOMAIN.com.

Also, Exchange 2000 server is on the internal network to process mail on
user accounts such as (e-mail address removed) and (e-mail address removed) who is
the same end user.

1) Is this separations sufficient to maintain security between the
external vs. internal domains? (Assume hardware firewalls are in place
etc.)

2) Would AD see inside.MYDOMAIN.com as the root domain or would it
be seen as some kind of child domain?

3) What other domain issues should I be concerned about?

4) What other Exchange issues should I be concerned about?

Thanks for any input and help.

Oren
 
In
XXXXXXXXXXX said:
Hi Everyone:

I am planning an Windows 2003 Active Directory domain for a client
company. The external domain name, for example, MYDOMAIN.com is
registered and has an active website on the Internet. The internal
domain name under AD is inside.MYDOMAIN.com.

Also, Exchange 2000 server is on the internal network to process mail
on user accounts such as (e-mail address removed) and
(e-mail address removed) who is the same end user.

1) Is this separations sufficient to maintain security between the
external vs. internal domains? (Assume hardware firewalls are in
place etc.)

2) Would AD see inside.MYDOMAIN.com as the root domain or
would it be seen as some kind of child domain?

3) What other domain issues should I be concerned about?

4) What other Exchange issues should I be concerned about?

Thanks for any input and help.

Oren
Click to expand...


This has been discussed extensively in these newsgroups. Honestly, to
summarize, create a different 1st level name for your domain, but use the
same second level name, eg, external is domain.com, the internal would be
domain.net or domain.local or domain.corp. It eliminates alot of security
issues and is less confusing for users and it will reduce administrative
overhead.

As for Exchange, Exchange will host any domain name, whether it's the same
as the AD name or not. I'm hosting 25 domain names (for clients) on my
Exchange server.

:-)

--
Regards,
Ace

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

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

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top