• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 2000 Server DNS?

D

Darksamie

Senior member
I am setting up a new Windows 2000 Server and doing something that I haven't done before. I am going to set it up with an internal IP address and it is going to serve approximately 30 clients. However, if I set it up with an internal IP address, then how will this affect the AD component? It won't be able to check the domain name against a DNS entry. So how would I go about setting it up for this?
 
I have read through most of those articles. However, they list what I do not want to do.

What I need is to install the server without a registered domain name. I don't want to expose the server to the Internet so I have an internal IP address via NAT. Therefore if I wanted to make the server yeah.yeah.com then it would try to look this domain up and see that it is not registered to the IP address I have given it. Will installing its own DNS server fix this?
 
Just add the DNS entries for the local computers onto your local DNS server, either manually or through dynamic DNS. That way when you try to resolve local addresses, your local DNS server will resolve it without having to query internet DNS servers.
 
Are you saying that the server and the clients won't have internet access?
Or that the server is receiving an ip address already through nat.

Explain your physical hardware setup first.

You don't have to have a registered domain name to set up DNS whether or not you're connected to the internet.

If you are behind a router or nat setup, you will have to delete the root entry "." under dns.

 
Sorry, I should have explained this a lot better from the beginning.

The setup involved:

Cisco 827 Router with NAT enabled.

Going to make the server have an internal IP of 192.168.0.10 or something similar.

What I am wondering is if I want to set up the server with the company domain name eg. yeah.com.au whether I make the server melbourne.yeah.com.au. How do I set this up so that the server in question will not poll DNS servers every 5 minutes to find that it is not registered?
 
Windows 2000 Server has a built in DNS server which you should be using for your domain. What you need to do is...

A) Install your DNS server, configuring your network as a forward lookup zone using the DNS server console

B) Add a host record for your server to your DNS table and

C) Configure your server to use itself as its own DNS server

This will keep your domain controller from querying internet DNS servers for your non existent domain. Now if you want the computers within your network to be able to communicate with each other based on DNS names, you also need to...

D) Add host records for each computer on your local network to your DNS table and configure them to use your server as their DNS server

It would also be wise to...

E) Reserve an IP address from your DHCP scope to statically assign to your server

Which can be done either through with your Cisco router or with the built-in DHCP server that also comes with Windows 2000 Server.

Hope that helps.
 
By default Windows server puts in 127.0.0.1 for its DNS address. You have to change this to your IP address that you assign to your nic, ie 192.168.0.1

Also don't forget to add your domain suffix 1st before installing DNS. If I remember correctly its rclick My computer, network properties, more. There should be a tab to add it there.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top