Use registered domain name as w2k FQDN...?

[fraKctured]

When installing w2k would it be best to use registered domain name...? Am
planning an Exchange server that will use the registered name for email.
All users would login to (e-mail address removed) for w2k domain.
Thanks

 

[Deji Akomolafe]

You don't HAVE to use real names for this purpose. Your internal domain name
could be myinternal.who and you will still be able to receive email for
myrealname.com and your user will be able to login as (e-mail address removed) IF
you add myrealname.com to your UPN ( see "Using Active Directory Domains
and Trusts Snap-in" in
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/manadsteps.asp)

HTH
--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon

 

[fraKctured]

Is it less problematic in the long run to a real domain name...?

 

[fraKctured]

Is there a "best practice" regarding the naming of a w2k domain that will
include an Exchange server wanting to use the same FQDN as the w2k domain?

 

[Deji Akomolafe]

Depends on whose book you are reading. But as far as Exchange is concerned,
your REAL (AD) domain name might as well be MarsRoverOpportunity.mars. There
are lots of companies out there whose business is to provide outsourced
email services for other companies (e.g. Hosted Exchange). The big players
will have hundreds of companies as their customers. Do you think they will
create hundreds of AD domains for each of these companies? This is one of
the reasons UPN was invented. Make good use of it.

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon

 

[Ace Fekay [MVP]]

In

Is it less problematic in the long run to a real domain name...?

Actually it's more problematic if you use your external name. This is due to
extra adminstration with possibly altering reg entries and manually creating
resources in DNS. It's actually ALOT easier and less admin overhead to use a
different name.

As Deji said, it will work either way with no problems.


--
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

 

[Ace Fekay [MVP]]

Depends on whose book you are reading. But as far as Exchange is

concerned, your REAL (AD) domain name might as well be
MarsRoverOpportunity.mars. There are lots of companies out there
whose business is to provide outsourced email services for other
companies (e.g. Hosted Exchange). The big players will have hundreds
of companies as their customers. Do you think they will create
hundreds of AD domains for each of these companies? This is one of
the reasons UPN was invented. Make good use of it.

I agree and for example, I'm hosting 20+ domains on my one Ex2k box.

--
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

 

[wax_yapple]

I don't know about Exchange 5.5 or 2000, but in my organization we ar
deploying Exchange 2003, and I've already hit a snap with regard t
using separate external domain names.

Over here we expect to deploy exchange for internal as well as mobil
users, and the requirement is that the mobile users should be able t
access their email using the same outlook 2003 client w/o any furthe
reconfiguration, whether within the organization or outside of it. Let
say the chosen organization name is corp.domain.com, whereas the domai
published to the internet (web, mail, etc) would be using domain.com
The external DNS server hosts only domain.com, and the internal DN
server hosts both domain.com and corp.domain.com as internal client
need to map domain.com to different IP addresses than the external
which go through different interfaces.

The problem lies where the exchange server, residing within the domain
is required to retain a fqdn of exchange.corp.domain.com, but publis
both internally and externally under the name of exchange.domain.com.

It's not a well-publicised fact, but to do so is impossible. Throug
my repeated testing, everytime i try to configure either an internal o
external client to find exchange.domain.com, it will redirect me t
exchange.corp.domain.com. Internal clients have no problem resolvin
this, but external clients are naturally unable to connect.
http://tinyurl.com/3fym3 has the details. You are required to publis
the fqdn (exchange.corp.domain.com) to your clients, and neither
separate host or alias on the dns server will help.

Has anyone else encountered this problem? I seem to find it strang
that it has never been encountered before, as my domain configuratio
seems to be quite standard

wax_yappl

 

[Kevin D. Goodknecht [MVP]]

In wax_yapple <[email protected]> posted a question
Then Kevin replied below:
: I don't know about Exchange 5.5 or 2000, but in my organization we are
: deploying Exchange 2003, and I've already hit a snap with regard to
: using separate external domain names.
:
: Over here we expect to deploy exchange for internal as well as mobile
: users, and the requirement is that the mobile users should be able to
: access their email using the same outlook 2003 client w/o any further
: reconfiguration, whether within the organization or outside of it.
: Lets say the chosen organization name is corp.domain.com, whereas the
: domain published to the internet (web, mail, etc) would be using
: domain.com. The external DNS server hosts only domain.com, and the
: internal DNS server hosts both domain.com and corp.domain.com as
: internal clients need to map domain.com to different IP addresses
: than the external, which go through different interfaces.
:
: The problem lies where the exchange server, residing within the
: domain, is required to retain a fqdn of exchange.corp.domain.com, but
: publish both internally and externally under the name of
: exchange.domain.com.
:
: It's not a well-publicised fact, but to do so is impossible. Through
: my repeated testing, everytime i try to configure either an internal
: or external client to find exchange.domain.com, it will redirect me to
: exchange.corp.domain.com. Internal clients have no problem resolving
: this, but external clients are naturally unable to connect.
: http://tinyurl.com/3fym3 has the details. You are required to publish
: the fqdn (exchange.corp.domain.com) to your clients, and neither a
: separate host or alias on the dns server will help.
:
It is not impossible.
Both of these names must be published in the public zone pointing to an IP
address on your router that is port forwarded to the exchange machine.

 

[Ace Fekay [MVP]]

Wax...see inline below...

In

I don't know about Exchange 5.5 or 2000, but in my organization we are
deploying Exchange 2003, and I've already hit a snap with regard to
using separate external domain names.

No problem..as I said, I host mutliple domains on my box. Ex55, Ex2k or
Ex2k3, no difference whatsoever. Matter of fact, Ex2k3 is pretty much almost
the same as Ex2k.

Over here we expect to deploy exchange for internal as well as mobile
users, and the requirement is that the mobile users should be able to
access their email using the same outlook 2003 client w/o any further
reconfiguration, whether within the organization or outside of it.

Then you should enable and use the new feature in Ex2k3 to support RPC over
HTTP. This allows Outlook2k3 clients without needing to open up a dozen
ports. Read the doc's on it. Cool stuff.

Lets say the chosen organization name is corp.domain.com, whereas the
domain published to the internet (web, mail, etc) would be using
domain.com. The external DNS server hosts only domain.com, and the
internal DNS server hosts both domain.com and corp.domain.com as
internal clients need to map domain.com to different IP addresses
than the external, which go through different interfaces.

This comes down to a split-horizon zone. Pretty much the same name internal
external. When you setup Exchange to host mutliple domains, the internal
domain name has nothing to do with the external, especially as long as you
DO NOT use any external DNS server addresses in ANY internal machine.

THe external MX record (no internal MX required) points to your outside IP,
(assuming NAT) and you port remap 25 to the Ex box. Then in Ex2k or Ex2k3's
recipient policy, you declare what domain suffixes (in the form of
@domain.com) that this server is authorative to receive mail on. That's it.
Those two settings will dictate whether Ex will receive mail from the
Internet or not for that domain name.

The problem lies where the exchange server, residing within the
domain, is required to retain a fqdn of exchange.corp.domain.com, but
publish both internally and externally under the name of
exchange.domain.com.

That is fine. Make sure the external DNS is NOT being used. Split zones,
however, require you to forcebaly make internal records that reflect an
outside resource, such as www, or ftp, etc, but since you are hosting Ex
internally, this doesn't have an affect.

It's not a well-publicised fact, but to do so is impossible. Through
my repeated testing, everytime i try to configure either an internal
or external client to find exchange.domain.com, it will redirect me to
exchange.corp.domain.com.

Then for internal usage, manually create a record called "exchange" under
your domain.com zone and give it the internal IP of the Ex box.

For external usage, make sure there is a record created on the external DNS
called "exchange" under the domain.com zone on that external DNS.

I really HOPE that you are NOT using the same DNS to host your external
data. This is practically impossible to make it work,. I am assuming you're
using an outside DNS (such as your ISP or registrar) to host your external
domain name. If you are using a DNS server on your location for the outside
name, it cannot be the same DNS that is used internally by AD and Exchange
and the rest of your network or you WILL have problems...

Internal clients have no problem resolving
this, but external clients are naturally unable to connect.
http://tinyurl.com/3fym3 has the details. You are required to publish
the fqdn (exchange.corp.domain.com) to your clients, and neither a
separate host or alias on the dns server will help.

Not sure why not? I've set this up repeatedly in similar scenarios for my
clients....

Has anyone else encountered this problem? I seem to find it strange
that it has never been encountered before, as my domain configuration
seems to be quite standard.

--
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