First off all ensure that your %SystemRoot%\System32\DNS folder (if it exists) is empty.
Then install the DNS Service from Control Panel, Network, Services, Add, DNS.
accept defaults and reboot.
Then
Start Menu, programs, Administrative Tools, DNS Manager.
From the DNS Menu, choose New Server ...
and then type in your DNS Servers IP address.
When it appears in the list, open it up (click on the plus next to it) and then right click on it and choose New Zone ....
Select Primary and choose Next.
Then type in your Domain in the top edit box(such as Mydomain.com), then just click in the edit box beneath it (and a a default entry such as mydomain.com.dns will be enmtered for you)
click Next. Then click Finish.
Then make sure that you know what your Internal IP Network ID is. I'll Assume (10.0.0.0 ie a subnet mask of 255.0.0.0).
Next set up a Revers lookup zone
right click on the DNS computer's IP address on the list again and choose New Zone ....
Select Primary and choose Next.
Then for the domain name type in the network ID in reverse without the zeros, eg in the example above that would be just 10, for a network id of 192.4 it would be 4.192) with in-addr.arpa. ie in thios example the zone name would be 10.in-addr.arpa. Again click in the box beneath it to get a default name of the file containg the entries.
To set up WINS INtegration.
Right click on the zone you created earlier and choose Properties, select the WINS Lookup Tab.
Enter the IP addresses of you Internal WINS Servers. (This theirfor measn that you wont need to add any static entries for your Internal clients AND it will work with DHCP clients.
Click the "Settings affect local Server" Only checkbox if you have other UNIX DNS Servers that will become secondaries.
Then If you are connected to the INternet.
Right Click on the DNS Server IP address in the DNS Manager program. Choose Properties.
Click on the Forwarders Tab. Select the USe Forwarders Check Box. Then add in the IP Addresses of your ISP's DNS Servers.
From the DNS Menu choose Update Server Data Files.
Exit the DNS Manager program.
AND
for good measure.
Reboot the server.
Good Luck
Ben
I Missed (Someone got an asnwer in first), so here's a comment anyhow now that I've typed all this stuff in.
Main Topics
Browse All Topics
by: redPosted on 1999-10-01 at 01:42:48ID: 2090168
When a person on a computer enters a name, it is resolved in this way: The local computer first looks into its own short list of known names to see if it knows the address for that name. If it does not, it looks up the address of it’s own DNS server and sends a message to the DNS server asking for the address of the name. If the DNS server knows the address for the name, it sends that information back to the user’s computer. If it does not, then it begins searching the Domain system for the address.
As an example, if the user enters the name WWW.Microsoft.Com, the DNS server will pick a dot server from it’s own list, and will ask for the address of WWW.Microsoft.Com. The dot server will usually respond with a message that means "I don’t know who that is, but go ask the .Com servers at one of these addresses". The DNS server then picks a server from the provided list and asks that server to identify the name. The .Com server will respond with a message saying "I don’t know that particular computer, but go ask the Microsoft.Com servers at one of these addresses". The server then picks a server from the list and asks it. Usually the Network level computer responds "WWW.Microsoft.Com is at this address...". The DNS server passes this address back to the user, and it also places that name and address in it’s own list so that it doesn’t have to go through the whole lengthy process if it get’s asked again any time soon.
In addition to the name and address information, DNS also provides information about how long a name should be remembered before the DNS server should forget it and go ask again. This is because computers do change addresses from time to time. Most names on the DNS system are good for about 8 days, then they expire and must be looked up again.
The Domain name used in this example is WLW.Com
There is a single class C of IP addresses numbered 205.217.146.0
There is a DNS server is named DNS at the IP address 205.217.146.198
There is a DNS server named NS1.Berkeley.Edu that is external to this network which is providing secondary DNS
There is an E-Mail server named MAIL at the IP address 205.217.146.200
There is an E-Mail server named Mail.ATT.Net that is acting as an external mail relay.
There is also a WWW server on the same hardware as the DNS server that should respond to the name WWW.
When you set up your own DNS configuration, you will need to change the specifics of these assumptions for your own setup. In particular:
Do not use the Domain Name WLW.Com
Do not use the IP addresses in 205.217.146.0
Do not use NS1.Berkeley.Edu as a secondary DNS (unless you make arrangements with them)
Do not use Mail.ATT.Net as an E-Mail relay host (unless you make arrangements with them)
Do not use Hostmaster@WLW.Com for your DNS E-Mail contact.
Begin by adding the MS DNS service to the NT Server system that will be hosting the service. Log onto the NT Server system using an ID that has Administrative privileges. Go to Control Panel, Network, select the Services tab, and click on Add. From the Network Services list select Microsoft DNS Server and click OK. The program may prompt you to place the NT 4.0 Server CD into your CD ROM drive. When it has completed loading the service, exit from the Network applet and re-boot your computer system.
When the system has finished re-booting, log on using an ID that has Administrative privileges. Go to the Control Panel, Services applet and verify that the Microsoft DNS Service has started. If it did not start, go to the Event Viewer and look for error messages to see why the service did not start.
To configure the DNS service, go to Start, Programs, Administrative Tools (Common), and select DNS Manager. This should bring up the Domain Name Service Manager window. Initially this should be empty except for a single entry showing Server List. Select the server to administer by going to DNS, New Server, and entering the IP address or Domain Name of the server to be administered, in this example DNS.WLW.Com. This should cause the program to connect to the DNS service that you just created. Highlight the server and double-click, this should bring up another level showing Cache.
The first zone you should create is the Reverse Arpa zone for the network. Hightlight the server name and select DNS, New zone. Select Primary Zone and click on Next. Enter the reverse arpa zone name, 146.217.205.in-addr.arpa, in the Zone Name field. Note that this is the most significant 3 parts of the Network Address in reverse order. Use the Tab key to tab past the Zone File field and accept the default name (146.217.205.in-addr.arpa.
The next step is to highlight the server (DNS.WLW.Com) and once again select DNS and New Zone. Select Primary Zone and click on Next. Enter the domain name, WWW.WLW.Com, in the Zone Name field and use the Tab key to tab past the Zone File field and accept the default name (WLW.Com.dns), and click on Next. Click on Finish and the program should create the zone file for you with the proper basic records automatically generated.
To add the host record for DNS.WLW.Com, highlight the WLW.Com zone and select DNS, New Host. Enter DNS in the Host Name field, 204.217.146.198 in the Host IP Address field, check the Create Associated PTR Record box, and click on Add Host. This should add the DNS A record to the WLW.Com database, and add the 198 PTR record to the reverse arpa database.
To add the host record for MAIL.WLW.Com, highlight the WLW.Com zone and select DNS, New Host. Enter MAIL in the Host Name field, 204.217.146.200 in the Host IP Address field, check the Create Associated PTR Record box, and click on Add Host. This should add the MAIL A record to the WLW.Com database, and add the 200 PTR record to the reverse arpa database.
To add the alias record for WWW that will point to DNS.WLW.Com, highlight the WLW.Com zone and select DNS, New Record. Select CNAME Record in the Record Type box, enter WWW in the Alias Name field, enter DNS in the Fort Host DNS Name field, 204.217.146.198 in the Host IP Address field, and click on OK. This should add the WWW CNAME record to the WLW.Com database.
To configure the database so that mail for users on the WLW.Com system is sent to the SMTP server at MAIL.WLW.Com, highlight the WLW.Com zone and select DNS and New Record. Select MX Record in the Record Type box, leave the Host Name field blank, enter MAIL.WLW.Com in the Mail Exchange Server DNS Name field, enter 10 in the Preference Number, and click on OK. This should add an MX record to the WLW.Com database for Mail.WLW.Com
To configure the database so that mail for users on the WLW.Com system can be relayed through the SMTP server at Mail.ATT.Net if Mail.WLW.Com is temporarily unavailable, highlight the WLW.Com zone and select DNS and New Record. Select MX Record in the Record Type box, leave the Host Name field blank, enter Mail.ATT.Net in the Mail Exchange Server DNS Name field, enter 20 in the Preference Number, and click on OK. This should add the MX record to the WLW.Com database for Mail.ATT.Net.
To configure the database to show that there is a secondary DNS server for the zone on NS1.Berkeley.Edu, highlight the WLW.Com zone and select DNS and New Record. Select NS Record in the Record Type box, enter NS1.Berkeley.Edu in the Name Server DNS Name field, and click on OK. This should add the NS record to the WLW.Com database for NS1.Berkeley.Edu.
Once the server is running you can use the program nslookup from the NT Command Prompt to query the server and verify that it is functioning properly.
Invoke nslookup by entering the command "nslookup" and note any error messages. The nslookup program should identify the name and IP address of the default server it is using, which should be the DNS server you have set up and are testing, and then it should display a command prompt ">". If you are testing the server from another system, or if the current system is pointing to another DNS server as it’s primary, use the nslookup command "server" to change servers (e.g. to set the server to DNS.WLW.COM use the command: server dns.wlw.com or server 205.217.146.198).
From the nslookup command prompt enter the command "dns". This will query the selected server for the IP address of the system named dns. On a system configured as shown in the above example the result of this would be:
> dns
Server: dns.wlw.com
Address: 205.217.146.198
Name: dns.wlw.com
Address: 205.217.146.198
Aliases: www.wlw.com
>
This tells you that the DNS server is responding properly and has the database properly loaded. Next enter the command "www.whitehouse.gov". This will cause the server to query out into the Internet DNS system for the IP address of WWW.Whitehouse.Gov. The result should be something similar to:
> www.whitehouse.gov
Server: dns.wlw.com
Address: 205.217.146.198
Non-authoritative answer:
Name: www.whitehouse.gov
Addresses: 198.137.240.92, 198.137.240.91
>
This tells you that the server is able to contact the rest of the Internet and resolve names by communicating with other DNS servers.
To check your Reverse Arpa, enter the nslookup command "set q=any" to display all information that is given as a result of a query. Then enter the nslookup command "198.146.217.205.IN-ADDR.A
> set q=any
> 198.146.217.205.IN-ADDR.AR
Server: dns.wlw.com
Address: 205.217.146.198
198.146.217.205.IN-ADDR.AR
146.217.205.IN-ADDR.ARPA nameserver = dns.wlw.com
146.217.205.IN-ADDR.ARPA nameserver = ns1.berkeley.edu
ns1.berkeley.edu internet address = 128.32.136.9
>
This tells you that the reverse arpa setup is functioning properly and is resolving PTR lookups.
To exit from the nslookup program use the command "exit".