Choosing a Namespace (Internal and External Domains?)

Choosing a Namespace (Internal and External Domains?)

Post by Sm9lR » Fri, 17 Mar 2006 13:56:35


I will be installing a Small Business Server 2003 Standard tomorrow which I
have experience with in the past. This particular installation will need to
be configured for the possibility of running Exchange server as the internet
mail server for the company.

I have used the .local domain extension in my past installations and
configured Exchange's POP Connector to poll every 15 minutes to a hosted POP
E-Mail Server such as network solutions. Initially, I will do the same for
this installation however; what will happen down the road if we want to host
our own e-mail server with Exchange? I realize that an MX record will need to
be set up to point to a static IP address. I do not understand the DNS issues
that will arise when trying to accomplish this. I guess to sum up my
questions:

- Should my internal domain name be a subdomain of the already registered
external domain? (Ex: "internal.company-x.com")
- Should I just use the default SBS wizzard to name the internal domain
"comany-x.local"

Again, this will be the only server which needs to be configured with the
possibility of running Exchange server included with SBS as the public E-Mail
server for the company.

I'm very confused and I have never installed Exchange as a public e-mail
server.
Any assistance will be strongly appreciated. Thank you and good luck to all
of your future endeavors.

Sincerely,

JoeF
 
 
 

Choosing a Namespace (Internal and External Domains?)

Post by Susan Brad » Fri, 17 Mar 2006 14:21:53

POP or MX/SMTP makes no difference.

.local or .lan is just fine.

Naming of Exchange's maiboxes and how it connects and gets email doens't
impact AD.

You should install many more of them this way. POP was designed as a
transition technology only.

 
 
 

Choosing a Namespace (Internal and External Domains?)

Post by Lanwench [ » Fri, 17 Mar 2006 14:25:33


The domain name you choose for AD doesn't really matter. By default, SBS
will suggest yourdomain.local. You can use this, or myrealdomain.com or
internal.mydomain.com - you just need to understand the ramifications of
each. For example, if you use myrealdomain.com and don't make some small
adjustments in your AD DNS, your users will not be able to find
www.myrealdomain.com on the Internet, because your server will think it's
entirely authoritative for myrealdomain.com and won't find www. This is not
insurmountable.

None of this is relevant when it comes to your Internet mail domain,
anyway - you can run AD using mydomain.local and fluffykittycats.com for
e-mail - the wizard will prompt you for this.

There's nothing particularly different/special about running Exchange as a
'public' mail server - I do suggest you take a look at
http://www.yqcomputer.com/ ,
but again, the SBS setup wizards (in particular, the CEICW) will help you
set this up.
 
 
 

Choosing a Namespace (Internal and External Domains?)

Post by SuperGumby » Fri, 17 Mar 2006 18:26:41

I agree with both Susan and Lawrence in their replies but _had_ to add a
little bit.

There is _no reason_ for your AD DNS name to in _any way_ be related to your
internet FQDN (domain.com). Keep up the good work of naming your AD with a
.local or .lan extension (I prefer .lan due to special handling some OS's
apply to .local), the CEICW will properly configure the Exchange to handle
email in your FQDN.
 
 
 

Choosing a Namespace (Internal and External Domains?)

Post by Leytho » Fri, 17 Mar 2006 19:47:27

In article <# XXXX@XXXXX.COM >,
XXXX@XXXXX.COM says...

I learned a LONG TIME AGO not to use a public domain name of any type. I
once, and just once, made the mistake of calling my domain STORMY.COM,
as it was a test network and I figured it was like a storm... Little did
I know that I had improperly configured DNS and when I noticed hundreds
of DNS request per hour hitting our firewall inbound, well.... Lets say
that I nicely contacted the offending public IP to learn that they owned
the domain name STORMY.COM and that our server was trying to replicate
DNS information with them......

From that day forward I have used .LAN as I don't personally like
.local. Yes, I know that at some point .LAN could be assigned as public,
but I'm willing to bet that the community will not make a serious
mistake like that with .LAN.

Do not do a .COM or .NET or anything public.

The only issue is replicating your public DNS settings to your internal
IP's so that people inside the network arrive at the same place they
would externally.

--

XXXX@XXXXX.COM
remove 999 in order to email me
 
 
 

Choosing a Namespace (Internal and External Domains?)

Post by Russ Grove » Fri, 17 Mar 2006 20:05:58

The Special Handling of some OS's he's talking about is MAC's

--

Russ Grover
SBS2003 Remote Support
Portland/Beaverton OR
Email: Sales at SBITS.Biz
Website: http://www.yqcomputer.com/
 
 
 

Choosing a Namespace (Internal and External Domains?)

Post by SuperGumby » Fri, 17 Mar 2006 22:21:23

and some Linux builds, it ain't MAConly.