Windows Forum

Ask something
Discussion Locked

DNS with private IPs

0 helpful
11 replies

by curlergirl

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
This is for an in-house network with 5 workstations. We're moving up to Windows 2000 server from NT 4.0. We have not been using DNS internally on our NT 4.0 servers, only WINS. All DNS services have been provided by our ISP, and we are using private IP addresses internally (10.10.10.x), using a router with NAT to connect to the Internet. At the same time we're moving to 2K, we're also moving to a DSL internet connection using a modem rather than router. I know that you can use a Win2K server as a router and use it to do NAT, so I have two questions. Can anyone tell me how do I set this up and/or should I be using Proxy Server or is there some other choice with Win2K? Also, how do I configure DNS internally if I'm using private IP addresses? I know the answers might be complex, so any good sources or references will gain you the points as well. (And don't tell me I don't really have to set up DNS, because I want to use learn AD and in order to do that I have to set up DNS.)

11 replies

by fgarber

One of the BEST DNS resources is this web site
http://www.dns.net/dnsrd/
They have complete info on dns.

by curlergirl

I checked out this web site - not my cup of tea. First of all, too UNIX oriented for a NT administrator. I appreciated the suggestion, but it really didn't help me.

by ebob

First, I think you will find that you will still be using a traditional router inside your DSL connection. Your DSL "modem" (not really a MO-DEM) replaces the analogue modem or DSU/CSU of other connection technologies. There are several good choicesfor DSL routers which also generally include firewall technologies, DHCP servers and so on, or you can look into using your existing router with some reconfig.

As for your internal DNS, you can just proceed. Since you have Windoze in house, just load up the MS DNS server service. A good way that I like to do this is to load on 2 servers (call them "A" and "B"). On "A", I configure my internal DNS name space. I also configure this box to NOT go to the Internet for resolution, by clearing out the root-cache file(s). So now "A" is what we call "authoritative" for my internal name space. Then I configure "B", and leave the root-cache intact. If at this time, I point all of my clients to use "B" as their DNS resolution, they will be able to resolve all of the names on the Internet, since "B" will (failing to find the resolution in its own cache) go out to the Internet and look up the resolution. It will also build up its own cache after awhile.

"But what about my internal name space?" you ask. Simple. On "B", create a secondary zone named by your name space, and tell "B" to get its info from "A". That is, tell "B" that "A" is "authoritative for your internal name space.

It seems complex but it really isn't once you get the basic setup running.

by ebob

(part 2)

The real beauty of this kind of setup is that it allows for growth, and changes without totally screwing up all of your users.

I've setup companies from 10 users to 50,000 users with this kind of setup. The big difference with the larger companies is setting up several more "B" type servers and a 3rd level ("C"?) at each location. These "C" servers do nothing but cache for the local users by passing all of their unknown requests to "B" (which in turn go to "A" or to the Internet), and build up their own local caches.

by ð

I currently have the setup at home of what your trying to do. You should setup the DSL Modem with a router. The LinkSys router works great with cable/dsl and it's only about $160 at buy.com.
Too setup NAT with Win2K, u need 2 NICs in the same PC.Configuring NAT is very simple, just follow the online instructions. The bad part of this is when u need to reboot the PC, every1 will be out of commission for internet access until it is back up.
I wouldn't setup proxy server unless you planning to filter out sites. Ineternet connection it's usually slower going through a proxy also unless the sites are cached in the Proxy Server.
For DNS Configuration/Info, goto http://www.microsoft.com/windows2000/en/server/help/ and look under networking,DNS. This should help you get a better understanding of how you want to setup DNS.

by ð

You should also look into setting up a firewall. The firewall software I like is Check Point. I heard BlackIce Defender is pretty good also...

Good Luck and have fun on you mission!!!

??

by kevin

Configuring Win2K DNS is relatively easy. The DNS Server is installed during Active Directory installation. You will need to enter your domain name and the wizard will finish the DNS installation.

You will then need to open the DNS Manager MMC. You can find this in 'Start\Programs\Administrative Tools'.

In DNS Manager, drill down to your server name and right click. Select 'New/Zone' and create a 'Reverse Lookup Zone' to go with the 'Forward Lookup Zone' that already exists.

Create host records for your servers as needed(email, web, etc...). Win2K uses Dynamic DNS(DDNS) so it is not necessary to create host records for the workstations. Win2K's DDNS will automatically register the workstations during logon. For this reason WINS is no longer needed.

As far as using private addresses, that is accomplished when you create your forward and reverse lookup zones and host records.

Hope this helps

by curlergirl

This is basic info that I understand. The problem which I am trying to solve is having two completely separate "zones" - one that is a private address space and one that uses an ISP's DNS servers for resolution of public IPs. I appreciate your attempt to help, but it really didn't answer my question.

This discussion is closed to new replies.