re: DNS settings for multiple servers without Internet Connection
Friday, March 28, 2008 at 7:27 am
Windows Server 2003 Annoyances Discussion Forum
Posted by Curt R
(766 messages posted)
Your domain controller, your DC, should point at itself as the DNS server. All
other devices in the domain (clients/servers etc) should point at the DC for their
DNS. During the procedure to promote a server to a DC (the first one in the
forest/domain that is) you are required to setup DNS. This is so that all clients
within the domain can be resolved to the DC for authentication purposes (ie: login).
Once you've got the DC setup and working if you want your clients to be able to
resolve requests outside the local zone (ie: surf the web) you must then forward
the DNS on the DC to your provider's DNS servers. All member servers within
a domain should have static IP's and should also have the DC's IP as their
DNS server. This will allow Active Directory to it's job properly and make all resources
in the domain available to all domain clients.
On Thursday, March 27, 2008 at 2:17 pm, John wrote:
>Help! I have a Win2k server controlling our domain (which for security reasons
is
>not connected to the internet). Everything worked fine with the Win2k workstations.
>
>I recently added a Win2003 server to the network, and cannot get it to talk to the
>Win2K server within the domain.
>
>Win2k workstations interact OK, but WinXP workstations take forever to logon, and
>hang often. They seem to generate "intrusion attempt" errors in the Win2K logs.
>
>Can someone help me define proper DNS settings on the two servers to make this work?
> I have tried every combination I can think of but cant get it quite right. I have
>a small network so I dont care whether I have to manually set the IP's or obtain
>auto.
>
>TIA...
|
