New Install Pending, please review setup

Question

Hello Everyone:
I'm posting this to get feedback on a proposed installation of OS X Server SL running on the on the newer mac mini platform. My main area of concern is to ensure that the DNS settings are correct from the get go. The server is actually already in production mode, but there are all kinds of problems with it and that's why my client found me, so the problems can disappear.
In evaluating the server it looks like most of the issues are related to bogus DNS settings and it looks like the server is too far along to be fixed without a reinstall, so I want to post my proposed settings ahead of time and get any feedback I can, save me as much head scratching as possible when the reinstall goes down.
Firstly, Intended Use:
The server is intended to make various lightweight services available to a group of around 10-15 users - most users spend 80-90% of their work time in office, but at least 4 users work out of the office and their homes, and 2 of these are also on the road constantly. In addition to those users there are about 5 or 6 users who a permanent teleworkers who live out of state.
The services desired to be used are:
-Open Directory management for all corporate users, local, mobile, and remote
-a contacts db shared by all users, regardless of location
-a calendaring system that everyone can read/write to, from any location (additionally some clients will not be mac/iCal clients, they will be windows based and need to participate in the calendaring service)
-Wiki site authoring to house internal documents, procedures, ETC
-file service to serve up available backup partitions to client machines (for both macs and PCs)
-VPN service for remote users, (mostly for connection to the backup service)
-Mobile Access, or else some other suitable configuration for remote users to connect to the iCal, AddressBook and Wiki services
At the moment we DON'T intend to run any mail exchanger services, nor any production websites
Initial Setup:
-Mac Mini SL Server connected via ethernet to Dual Band Time Capsule
-Time Capsule connected to broadband connection with one static IP from ISP
-Time Capsule NAT is enabled forwarding relevant ports on to Mac Mini SL Server
-Time Capsule handles DHCP:
--DHCP Reservation for MM SL Server: 10.0.1.11
--LDAP Server points to: 10.0.1.11
--DHCP pool ends at .200 (.201+ reserved for VPN clients)
-Additionally, Time Capsule DNS points to 10.0.1.11, domain name set to <Mac Mini SL Server FQDN> (to be figured out below)
Mac Mini SL Server, Network and DNS:
---One quick note, initially this company had just a dynamic IP for the broadband connection, and I was going to set up a dyndns dynamic domain name for them that pointed to their current IP via dyndns client daemon, but since I have to go for the full reinstall the company has elected to use one of its spare registered domain names
-Mac Mini's network adaptor's DNS is set to loopback, 127.0.0.1
From this point - things get rather specific:
In Server Admin under Zones, I shouldn't need a complex set of records but I have had a real hard time figuring out what the proper configuration for the primary zone and the FQDN.
On the outside of the local network where the MacMini server lives - we have an ISP provided static IP, and additionally we have a registered domain with points to the ISP static IP - since this is a registered domain part of my confusion is in whether the MacMini's FQDN ought to be the same as our registered domain on the outside. The registered domain is what folks on the outside will use to connect to the server's services on the inside.
Here I will attempt to outline my proposed DNS settings, which I am hoping some of you will be kind enough to give me feedback on:
-Registered Domain Name: thecorpteam.com
---Primary Zone
-Primary Zone Name: thecorpteam.com.
-Nameservers: Zone: thecorpteam.com. Nameserver Hostname: thecorpteam.com.
--Machine Record
-Machine Name: server
-IP Addresses: 10.0.1.11
--Machine Record
-Machine Name: thecorpteam.com.
-IP Addresses: 10.0.1.11
---Reverse Zone
-Reverse Zone Name: 1.0.10.in-addr.arpa.
-Nameservers: Zone: 1.0.10.in-addr.arpa. Nameserver Hostname: thecorpteam.com.
Additionally under the DNS Settings Tab
-Accept recursive queries from the following networks: is set to 'localness'
and
-Forwarder IP Addresses: is set to the ISP's DNS servers
These are the settings that I THINK will work, but I'm not sure by a long shot so please jump in if you see anything amiss.

Answer 1

So under the Nameservers for the Primary (and the Reverse that is created) the Nameserver Hostname ought to be the local server the IP for the local server should be sufficient for this?
Running through the full loop and in relatively general terms... Domains and subdomains are organized into zones. Zones have name server(s). Name servers themselves usually host names, sometimes within their own zones and sometimes within the zone of another name server or pool of name servers. Host names also have IP addresses. DNS server references within the clients will reference and will use the IP address(es) for the name servers, as they don't (yet) have a name server to translate the names.