Windows Server

D Morgan · Guest

What are the right Windows Server 2003 install-time choices for
assigning name and IP to the machine and/or active directory domain,
and their relationship to DNS?

I use private IPs in my mixed-platform home network. It sits behind a
router which uses my sole, static, public IP on the external
interface. The router does NAT address translation for the other
machines. Plus I have a domain name, which I've matched n DNS to my
public IP.

I want to learn Windows Server by setting one up in my home network.
But I think Microsoft combines the public DNS system with its own
active directory system in some ways. As the name for my active
directory domain, I'm supposed to choose my same, pre-existing DNS
domain name I think. However that name matches to an IP which won't be
that of the Windows Server box (it'll have a private IP).

I want to get it right the first time (install time). What's the
wisdom on this architecture. Is it something people do all the time?
It is something that can't be done, the Server must front to the
internet as the router? Any tips how to avoid later complication?

Leathal · Joined: 23 Feb 2005 Posts: 37

Idealy you should use your internet domain name as the name of your DNS server. Example: microsoft.com

As for the IP address if the gateway of your network points to 192.168.1.1 which is your router set the server up as:

IP: 192.168.1.2
SUB: 255.255.255.0
GW: 192.168.1.1
DNS1: 192.168.1.2
DNS2: empty
WINS: 192.168.1.2 (if you have it installed)

You can use example; microsoft.local; as your DNS name however as I found out after running the latest best practice analyzer tool for Exchange 2003 Microsoft now recommends you don't use .local at all if you are planning to use Exchange.

Leathal

	Windows Server Forum Index -> DNS	All times are GMT
Page 1 of 1