Windows Forum

Ask something
Discussion Locked

Configuring DNS in Win2K.

0 helpful
5 replies

by sneeks

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I need help setting up DNS in an Active Directory domain. I have 1 domain controller and I want it to also run DNS. My network addressing is private (10.x.x.x) behind a firewall that translates to a public address. Currently, we use our ISP's name servers. But my DC also has a public address (I can access it from the outside).

Ideally, I would like to setup DNS so it does all the queries itself. If it isn't possible, then I can keep this DNS private and have it query my ISP's name servers for resolving.

I'm new to DNS and especially Win2k DNS, so I would appreciate a sort of step-by-step from someone who has experience in this.

Worth 1000 points.

Thanks

5 replies

by z

The trick is to setup forwarders. Forwarders are your ISP's DNS servers that will handle external queries that aren't in your DNS server's cache. In the DNS MMC window, right click on your server name, go to properties and under forwarders, put inyour ISP's DNS servers. You will also need a zone which is simply your domain name - there is a forward and reverse lookup zone. Forward looks up ip addresses based on name given and reverse is the opposite. Then you can tell all your desktops to query your DNS server and it will query the ISP for outside addresses and build a cache table that will improve your lookup time. Other than that, ad an A record (Windows may call it 'host')for all your servers and internal web sites. I bought a book called "DNS on Windows NT" by O'reilly and it was very helpful. I know you're using 2000 but the principle is the same. Remember, this is just a very basic setup ... Good luck.

by ian mclaws

I do agree with the first poster, all you really need to have your own DNS server to resolve internally and still use the ISP DNS servers for external resolution is to add forwarders to your DNS.
You state in your question that you wish to have your DNS server configured so "it does all the queries itself". DNS doesn't work like that. DNS is a distributed database, no single server has all name resolutions. Your DNS server will use other DNS servers to resolve, or partially resolve, addresses.You can limit the involvement of other DNS servers by adding entries to your DNS zone file. A DNS server checks its own database for a resolution before asking other DNS servers for help.
Steps for installing your DNS service:
1) Ask your ISP to add an entry into the DNS domain database that is one step above yours. eg: if the name of your DNS server is server.company.isp.com, you would ask the ISP to add an NS entry to its isp.com DNS domain.
2) Verify that all DNS details (domain name, DNSserver search etc) are properly entered on the server that will be the DNS server BEFORE installing the DNS service.
3) Install the DNS service
4) In the MMC - DNS console, add a primary zone to your server, making sure that its name matches your DNS domain name
5) In the properties of this zone, configure at least one forwarder (usually the servers primary DNS search server, as configured in step 2, as post 1 says
6) Add entries for your servers, and any other systems that you wish this DNS server to be able to resolve internally. If you are using DHCP, and you have dynamic clients that must be listed, you can enable dynamic DNS updates on the properties of the zone, and on the DHCP clients. (The old way was to use client reservations in DHCP, then add entries that matched them in DNS....still valid)
Bear in mind, for this to work properly you should have a permanent connection to your isp.

Good luck

Ian

This discussion is closed to new replies.