Help understanding if DNS required

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

Thanks.

 

[jockojem]

Yes you need DNS to run AD. AD uses a particular type of record (SRV) to locate AD services.

In this situation you have two options -

1 Install your own dns which would be authorative as far as AD is concerned for your domain. No zone transfers or clients would obviously be configured other than the box itself. DNS should then be configured to use the isp dns for the internet and resolution of mx records.
2 The alternative is to query your hosting company as to whether their dns supports (permits) dynamic updates and srv records. Configure your server then as a client for this server. You would need the zone file creating in advance and I daresay would probably have little or no direct control over records if a problem arises.

I never like to query people's motivations in posts because I know I have asked some seemingly illogical questions before and recieved some smart alec replies when all along I have had my reasons...... however is exchange the best tool for the job here? Exchange is best suited to an enterprise environment. As your clients are not going to be in your domain (they will not be able to contact a dc for auth) you must be using only pop3/smtp etc. I wonder if you have considered other products that will enable you to offer these services without the extra admin overhead of AD?

Jem

 

[pcarver]

Just a few observations:

1) what would I call this domain... mydomain.com
2) can I call the box whatever... mybox.mydomain.com
3) I will be hosting about four different domains on the box and the associated emails for these. I would rather just use pop3 and smtp from 2003, but it doesn't appear to allow distro lists and forwarding; correct?

Thanks for the help.

 

[jockojem]

Hi There

Not sure about Q3. I'm not a messaging/exchange guru. You might be wise to post on the exchange board about implementation.

As for 1 and 2. Yes the domain name can be arbitary - in fact it is probably good practice in your instance not to use one of your internet names. I am assuming your internet isp will handle cnames and mx records for the box on the internet.

Jem

 

[technome]

Exchange is heavy duty, and will cost you plenty; not easy to install or maintain. Unless in a corporate atmosphere, it is overkill.

A program like IMail ( cheap, powerful and flexible) from Ipswitch will do what you need. Simple installation and support is very good. After you get you DNS setup correct, you could possible send out mail in 20 minutes ( if you had previous install experience)

Do you know about the other email "necessities", this is where it get bit expensive. If you don't scan email with multiple AV products your placing clients at unnecessary risk (liability). The last email server I setup I had 3 anti virus scanners checking all mail. For this you need an add-on, in Imail's case you use "Declude", coupled with inexpensive AV engines, about $ 1200.00. Are you going to employee spam filters, about another $ 1000.00

For IMAIL you could skip AD, will run on Win2000 professional. Recommend win2000 server or XP server, and at least raid 1. A 2.4 Ghz machine with 1gi ram would be plenty.

Dns.... personally if you are going with Server and or AD and if you have a registered domain name such as mydomain.com, it would created less problems if your internal domain is a sub domain of the registered name eg. mail.mydomain.com. An alias in DNS can be created to shorten it to mydomain.com. If you get the server Os you can run your own DNS. Dealing with an ISP to make changes to DNS can be a royal pain. What ever mail system you get, make sure you disable "relaying" of mail; I also place a footer in all outgoing email explaining, my system does not "relay" and the virus scanners I use, this way the big ISPs ( like AOL )let your mail through with no problem.
Don't forget "reverse lookup pointers" in DNS.

For an indepth DNS explaination I would recommend Mark Minasi's "Windows Server 2000" or 2003. This guy knows DNS, with best secure solutions.

Paul