Active Directory setup - Microsoft Exchange

Hi,

AD and exchange can share the same domain name without any problems.

Leif

"Jeff" <jhomason2003@yahoo.com> skrev i en meddelelse
news:%23RGMhviqEHA.3980@TK2MSFTNGP12.phx.gbl...
> I'm currently running AD on my internal domain as company.com,
> and I have another seperate domain running Exchange 5.5 with emails
> being answered as @company.com.
>
> I'm migrating to Exchange 2003, and need to setup AD, but was wondering
> if that AD could also be called company.com, because that is how the
> emails will be setup.
>
> Jeff

Jeff wrote:
> I'm currently running AD on my internal domain as company.com,
> and I have another seperate domain running Exchange 5.5 with emails
> being answered as @company.com.
>
> I'm migrating to Exchange 2003, and need to setup AD, but was
> wondering if that AD could also be called company.com, because that
> is how the emails will be setup.
>
> Jeff

The AD domain name and e-mail domain names don't need to match - many people
will recommend that your AD name be company.local or some other 'fake' name.
You can add your company.com domain to the recipient policy in ESM and use
it as the default...

Hello Jeff,

Having your email domain name and AD domain name the same although
possible can make it more difficult to set up a secure DNS environment.
AD will require to resolve private local service locator records and
other email messaging domains will require to resolve the public email
domain MX (Mail Exchange) records.

--
--
John Negus
MSEtechnology


"Jeff" <jhomason2003@yahoo.com> wrote in message
news:%23RGMhviqEHA.3980@TK2MSFTNGP12.phx.gbl...
> I'm currently running AD on my internal domain as company.com,
> and I have another seperate domain running Exchange 5.5 with emails
> being answered as @company.com.
>
> I'm migrating to Exchange 2003, and need to setup AD, but was
> wondering if that AD could also be called company.com, because that is
> how the emails will be setup.
>
> Jeff

John Negus wrote:
> Hello Jeff,
>
> Having your email domain name and AD domain name the same although
> possible can make it more difficult to set up a secure DNS
> environment. AD will require to resolve private local service locator
> records and other email messaging domains will require to resolve the
> public email domain MX (Mail Exchange) records.

Not really a security issue so much as an admin one. And the MX records
don't matter - clients don't use them. You don't need internal MX records.

>
> --
>
> "Jeff" <jhomason2003@yahoo.com> wrote in message
> news:%23RGMhviqEHA.3980@TK2MSFTNGP12.phx.gbl...
>> I'm currently running AD on my internal domain as company.com,
>> and I have another seperate domain running Exchange 5.5 with emails
>> being answered as @company.com.
>>
>> I'm migrating to Exchange 2003, and need to setup AD, but was
>> wondering if that AD could also be called company.com, because that
>> is how the emails will be setup.
>>
>> Jeff

By setting up a secure DNS environment I meant that your "private" (SRV
and A) records for company.com will have to be kept separate from you
public (MX, A or CName) records for company.com to keep you private DNS
zone information secure (ie not visible to those who do not need to know
them).


--
--
John Negus
MSEtechnology


"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
message news:eNz3Kl1qEHA.2796@TK2MSFTNGP10.phx.gbl...
> John Negus wrote:
>> Hello Jeff,
>>
>> Having your email domain name and AD domain name the same although
>> possible can make it more difficult to set up a secure DNS
>> environment. AD will require to resolve private local service locator
>> records and other email messaging domains will require to resolve the
>> public email domain MX (Mail Exchange) records.
>
> Not really a security issue so much as an admin one. And the MX
> records
> don't matter - clients don't use them. You don't need internal MX
> records.
>
>>
>> --
>>
>> "Jeff" <jhomason2003@yahoo.com> wrote in message
>> news:%23RGMhviqEHA.3980@TK2MSFTNGP12.phx.gbl...
>>> I'm currently running AD on my internal domain as company.com,
>>> and I have another seperate domain running Exchange 5.5 with emails
>>> being answered as @company.com.
>>>
>>> I'm migrating to Exchange 2003, and need to setup AD, but was
>>> wondering if that AD could also be called company.com, because that
>>> is how the emails will be setup.
>>>
>>> Jeff
>
>

John Negus wrote:
> By setting up a secure DNS environment I meant that your "private"
> (SRV and A) records for company.com will have to be kept separate
> from you public (MX, A or CName) records for company.com to keep you
> private DNS zone information secure (ie not visible to those who do
> not need to know them).

Of course - split brain DNS means just that. The two never have to meet up.
And never will, if you aren't trying to point your public DNS at your own
private DNS servers.

But I can pretty set up an isolated AD domain called microsoft.com, and
although it would drive me nuts as I couldn't easily get to Microsoft
websites, it won't actually break anything, non?

Bottom line: don't try to host your public DNS in house unless you have
dedicated isolated DNS servers for it and really know what you're doing. :-)


>
>
> --
>
> "Lanwench [MVP - Exchange]"
> <lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
> message news:eNz3Kl1qEHA.2796@TK2MSFTNGP10.phx.gbl...
>> John Negus wrote:
>>> Hello Jeff,
>>>
>>> Having your email domain name and AD domain name the same although
>>> possible can make it more difficult to set up a secure DNS
>>> environment. AD will require to resolve private local service
>>> locator records and other email messaging domains will require to
>>> resolve the public email domain MX (Mail Exchange) records.
>>
>> Not really a security issue so much as an admin one. And the MX
>> records
>> don't matter - clients don't use them. You don't need internal MX
>> records.
>>
>>>
>>> --
>>>
>>> "Jeff" <jhomason2003@yahoo.com> wrote in message
>>> news:%23RGMhviqEHA.3980@TK2MSFTNGP12.phx.gbl...
>>>> I'm currently running AD on my internal domain as company.com,
>>>> and I have another seperate domain running Exchange 5.5 with emails
>>>> being answered as @company.com.
>>>>
>>>> I'm migrating to Exchange 2003, and need to setup AD, but was
>>>> wondering if that AD could also be called company.com, because that
>>>> is how the emails will be setup.
>>>>
>>>> Jeff