Hi Linn -

What other server are you going to be using for DNS?  And what other
physical location is it going to be at?  And separate Internet provider,
etc.  To host public DNS records you should have a minimum of two servers at
two separate physical locations with separate internet connections with
separate ISPs.

Standard recommendation is not to use SBS for hosting public DNS records -
one major reason is that Windows doesn't handle split DNS very well if at
all, which means that your internal DNS will be accessible to the outside.
There are too many cost-effective out-source options available for
controlling DNS records to justify hosting public DNS inhouse, especially on
an SBS . . .

Just my $0.02

Linn,

First of all are you using premium?

Second, if your server is in a DMZ the firewall is not providing any
security. If the SBS server is only going to be a webserver you only need
ports 80 and 443 open. Unless you are going to do FTP, mail, remote admin,
etc.

DNS is installed by default on SBS. It is a requirement of AD. Unless you
have just installed the OS, DNS is already running.

Your configuration depends on the version of SBS you are running.

Regards,
Jeff Loucks
      Available Technology ?
           Solutions For Professionals ?
                 www.availabletechnology.com

this would be a REALLY POOR idea for your "one" server that contains all of
your data from a security stand point.