Re: Choosing a Namespace (Internal and External Domains?)

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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.

JoeF wrote:

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


.