Configuring DNS between two non-trusted forest??

Question

We currently have a 2003 domain/forset setup and now have a new 2008 domain/forest setup running server core 2008 for the DCs.  What is the most secure way to setup DNS between the two forest without a trust so we can communicate for remote management
of the server core DCs?  We have configured remote management for the server core DCs via the server core console, but there seems to be some type of DNS issue still out there.  We do not want to create a trust between the two forest because the
2008 forest will be our DMZ.

Answer 1

Hi Tony,
I only forced the .local to display in the initial config one time, amongst several other fresh installs in which I just left it alone.
I did a fresh install, followed standard protocol for the initial config, and configured DNS.
In both cases (before and after I configured DNS) the keys you asked about in the preferences.plist are:
<dict>
<key>Network</key>
<dict>
<key>HostNames</key>
<dict>
<key>LocalHostName</key>
<string>server</string>
</dict>
</dict>
<key>System</key>
<dict>
<key>ComputerName</key>
<string>server</string>
<key>ComputerNameEncoding</key>
<integer>0</integer>
<key>HostName</key>
<string>server.nineridge.com</string>
</dict>
</dict>
...yet again when I go to promote the OD to a master, the Kerberos Realm autofills SERVER.LOCAL.
In case this is helpful, here is the output of the various checks:
server:~ sadmin$ host server.nineridge.com
server.nineridge.com has address 192.168.9.254
server:~ sadmin$ host 192.168.9.254
254.9.168.192.in-addr.arpa domain name pointer server.nineridge.com.
server:~ sadmin$ nslookup server.nineridge.com
Server: 192.168.9.254
Address: 192.168.9.254#53
Name: server.nineridge.com
Address: 192.168.9.254
server:~ sadmin$ sudo changeip -checkhostname
Password:
Primary address = 192.168.9.254
Current HostName = server.nineridge.com
DNS HostName = server.nineridge.com
The names match. There is nothing to change.