I want to put my own server in a co

[pcarver]

I want to put my own server in a co-location factility. Here is my configuration. I have an existing domain name and it's in my provider's DNS. My server will be running Exchange so I can do email (need forwarding, aliases, and lists...so I need more than just POP3 and SMTP that come with 2003).

From what I understand via reading...

In order to use Exchange, I need Active Directory and a domain controller. In order to use Active Directory, I need DNS Server installed.

Since this is the only server in the domain, I assume it has to be the primary. I'm most confused about DNS. I don't want to run a full-fledged DNS since I don't have secondary. Do I really have to? If so, would I make the name of my domain simpley the name of my internet domain as
xxx.com?

I will be doing email for about four domains and really need distro lists and forwarding.


Thanks.

 

[jimmysays]

Why are you co-locating your equipment?

Exchange will allow you to host multiple domains with seperate public folder access through OWA. SMTP and POP access through Outlook or Outlook express will allow e-mail but not public folder access (which doesn't matter unless public folders are required by your clients).

You should be able to run the primary DNS yourself, on your co-located server. Your ISP or co-location company probably include secondary DNS support with your contract. If not for a small fee they will.

There are allot of options. I would need more specific information before a clear answer can be given.

Split your questions into the tasks you wish to perform. Maybe even include a scope of your project so we have a better idea of what your business plan is.

Jimmy