Adding another machine to Primary Zone

Question

Adding another machine to Primary Zone
I have a good split-DNS configuration that has been working without issue for some months now since I installed OS X Server Snow Leopard (Mac Mini) at my company's office. We have another machine used as a file server (Mac Pro), without the dedicated server OS installed.
We want to add a virtualized instance of Windows Server 2008 R2 as a guest OS on the Mac Pro via VMWare Fusion. We want to use this Windows Server instance to host some private web based services for our corporate team (intended to be reachable from within the local private network, and remotely, from the public internet (with proper authorization to access only).
So far so good:
-WinServer2008R2 installed as a guest OS on the host Mac Pro
-WinServer's virtual NIC is in bridged mode (joins the host OS's physical network)
-WinServer instance configured with an IP 10.0.1.33, which is set aside and reserved for the WinServer by the local DHCP service on the same network
-WinServer successfully installed and tested IIS7 - both localhost from the WinServer instance and http://10.0.1.33 from other machines on the local private network (and from remote VPN clients) resolve to the WinServer's IIS default page properly.
Where I am stumbling now in configuring DNS on the Mac Mini to properly forward requests aimed at the WinServer instance.
DNS for the local domain is controlled by the Mac Mini. The configuration has been quite simple up to now, as that has met our needs. Just one Primary Zone and one Reverse Zone. We have an external DNS service from DYNDNS that handles any request for our domain from the external public internet. For now I'm not concerned with altering the external DNS service. Once I get the name service to properly resolve requests for the WinServer instance from the local domain, then I'll move onto matching up the external DNS.
--Primary Zones
Primary Zone:
Primary Zone Name: ourcompany.net.
Nameservers: Zone: ourcompany.net. Nameserver Hostname: server.ourcompany.net.
--Records
Machine Record:
Machine Name: server.ourcompany.net.
IP Address: 10.0.1.11
--Reverse Zones
Reverse Zone:
Reverse Zone Name: 11.1.0.10.in-addr.arpa.
Nameservers: Zone: 11.1.0.10.in-addr.arpa. Nameserver Hostname: server.ourcompany.net.
Resolve 10.0.1.11 to: server.ourcompany.net.
The -checkhostname command returns:
Primary address = 10.0.1.11
Current HostName = server.ourcompany.net
DNS HostName = server.ourcompany.net
The names match. There is nothing to change.
dirserv:success = "success"
So I attempted to add a Machine Record to the Primary Zone with the following settings:
Machine Record:
Machine Name: dash.thewcateam.net.
IP Address: 10.0.1.33
When I did this it added the following Reverse Zone:
Reverse Zone:
Reverse Zone Name: 1.0.10.in-addr.arpa.
Nameservers: Zone: 1.0.10.in-addr.arpa. Nameserver Hostname: server.ourcompany.net.
Resolve 10.0.1.33 to: dash.ourcompany.net.
And with the following records added I don't seem to have a proper resolution to 10.0.1.33 when requesting dash.ourcompany.net.
I'm wondering where I should look next in troubleshooting this issue. Any pointers or advice would be very appreciated.

Answer 1

Remove the "Reverse Zone Name: 11.1.0.10.in-addr.arpa."
It's probably left from when you first configured the server.
Though the "Primary Zone Name: ourcompany.net." seems correct.
Then update the 10.0.1.11 record so it's added to the right reverse zone - "1.0.10.in-addr.arpa."
In a MacPro we run VM Ware on a separate interface (en1/"Built in 2") that is forced up using a LaunchDaemon. "Built in 2" must be active in Network config in OS X but don't need to be configured (red "LED").
That way the MacPro can use it's own IP on the en0 interface without disturbing en1 and vice versa.