This configures the Netra Server as a DNS Server with a list of DNS root servers to query. If you configure the Netra server as a DNS server, you would normally configure it to be a DNS client of itself. Set up the server before you configure the client.
From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.
Under "DNS Server," click Configure as a basic DNS Server.
The Basic DNS Server Configuration page is displayed.
Complete the form using the information in following table.
Table 3-7 Basic DNS Server Configuration
After successfully configuring a DNS server, the module checks to see if the DNS server is configured as a client of itself. The Operation Successful message, displays information about the server configuration, and if the DNS server is not configured as a DNS client of itself, provides a link to the DNS client configuration form.
If you change the name of the domain in which the server resides, the DNS resource files for the primary domains are updated with respect to the contact address and the name server address of the Netra server. Review the individual primary domains to update any other references to the old domain name.
From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.
The DNS Server Administration page is displayed.
Choose one of the following:
To modify a Basic DNS server, click Modify, and make the changes in the form using Table 3-7 as a reference.
To delete a Basic DNS server, click Delete, then confirm the operation.
From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.
Under "DNS Server," click Configure as a internal root server).
The Configure as an Internal DNS Root Server page is displayed.
Complete the form using the information in following table.
Table 3-8 DNS Internal Root Server Configuration
Create the primary domain corresponding to the name entered in the DNS Domain Name field with the "Add a Primary Domain" form.
The Operation Successful page displays information about the server configuration, and if the Netra server is not configured to be a DNS client of itself, informs you of this and provides a link to the DNS client configuration form.
If you change the name of the domain in which the server resides, the DNS resource files for the primary domains are updated with respect to the contact address and the name server address of the Netra server. Review the individual primary domains to update any other references to the old domain name.
From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.
The DNS Server Administration page is displayed.
Choose one of the following:
To modify a DNS internal root server, click Modify, and make the changes in the form using Table 3-8 as a reference.
To delete a DNS internal root server, click Delete; then confirm the operation.
From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.
Under "DNS Server," click Add a primary domain.
The Add DNS Primary Domain page is displayed.
Complete the form using information in the following table.
Table 3-9 DNS Primary Server Administration
DNS Primary Server Information |
Description |
---|---|
Primary Domain Name |
The name of the primary domain, for example: mydomain.com. The name you enter is assumed to be fully qualified whether or not it ends in a trailing period. |
Host Names/Host Addresses |
The host names and corresponding host addresses of the hosts within the domain. For example, myhost 1.2.3.4 |
Host Aliases/Host Names |
Enter alias names for hosts in the domain followed by a known name of the host. For example, www myhost |
Mail Addresses/ Preferences Mail Servers/ |
Use this field if people are expected to send mail to the domain rather than directly to the mail server. Each entry consists of the name of the domain, followed by a preference value and the host name of the mail server. For example, if you are entering data for mydomain.com in which the server that deals with mail is called mailhost, make an entry as follows: mydomain.com. 5 mailhost The preference value is an integer: the lower the value, the higher the priority of that mail server. |
Domains/ DNS Servers |
Enter records for other DNS servers. Each record consists of the name of the domain that the server is responsible for followed by the name of the server. You do not need to create a record specifying that the Netra server is the name server for this domain - the Netra software does that automatically (the record is shown on the success page, and also on this form if you modify the domain data at a later time). |
Click OK.
If the Netra server is not configured to generate reverse maps automatically, the success page displays a link to the DNS Reverse Map Generation form.
From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.
The DNS Server Administration page is displayed.
Choose one of the following:
To modify a DNS primary domain, click Modify, and make the changes in the form using Table 3-9 as a reference.
To delete a DNS primary domain, click Delete, then confirm the operation.
It will be useful to configure a sample primary domain configuration. This example sets up a domain called comedy.cartoon.net on the name server stimpy. There are various hosts in the domain that have different functions.
In the Primary Domain Name field, specify:
comedy.cartoon.net
In the Host Names/Host Addresses field, type a list of those hosts whose presence are to be broadcast to any machine that can connect to this DNS server. For this example, type ren and stimpy, and for a host called homer that resides in (located) in the DNS subdomain black.comedy.cartoon.net, type homer.black.
ren 118.1.1.2 homer.black 118.2.1.2 stimpy 118.1.1.3
The Internet community uses conventional names for hosts that provide certain types of services, in order to make them easy to locate. For instance, the WWW server for a domain is usually known as www.domain, and an anonymous FTP server is typically called ftp.domain. On comedy.cartoon.net, ren is an FTP and WWW server, while stimpy is a name server. Standard aliases for these machines are added into the Host Aliases/Host Names field. For example:
www ren ftp ren ns stimpy
stimpy is going to handle mail sent to comedy.cartoon.net, so an MX record needs to be created.
comedy.cartoon.net. 5 stimpy
Finally, to the name server records, are added a single record for a host called homer that resides in a subdomain of comedy.cartoon.net called black - homer.black.comedy.cartoon.net is the name server for that domain.
black.comedy.cartoon.net. homer.black.comedy.cartoon.net.
If a domain contains subdomains that are maintained on another DNS server, the domain data must include records for the DNS servers for the subdomains. Note that in our example, since homer resides in the black subdomain, a Host Name/Host Address record for homer had to be added so that stimpy can reach it.
There is no need to create a name server record which says that stimpy is a name server for comedy.cartoon.net, because the Netra j software does that automatically. Next time you visit this form to modify the domain, the following record shows up next to the one for homer.
comedy.cartoon.net. stimpy.comedy.cartoon.net.
Use this form to configure the Netra server to generate reverse maps (address to name records) corresponding to the host records in the primary domains for which the server is responsible automatically. A link to the form appears on the DNS Server Administration form if the Netra server is responsible for at least one primary domain. The reverse maps will be based on the first three octets of the IP address, which assumes that the Netra server is authoritative for the entire block of class C hosts.
From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.
Under "DNS Server," click Enable Automatic Reverse Map Generation.
The DNS Reverse Map Generation page is displayed.
Click OK.
From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.
Under "DNS Server," click Disable Automatic Reverse Map Generation.
The DNS Reverse Map Generation page is displayed.
Choose one of the following:
Disable automatic reverse map generation. Leave the current reverse maps in place. This leaves the reverse maps in place, but stops updating them.
Disable automatic reverse map generation. Remove the current reverse maps. This both stops updating reverse maps and removes the current files.
Click OK.
From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.
Under "DNS Server," click Add a secondary domain.
The Add DNS Secondary Domain page is displayed.
Complete the form using the information in the following table.
Table 3-10 DNS Secondary Server Administration
DNS Secondary Server Information |
Description |
---|---|
Secondary Domain Name |
The name of the secondary domain. A secondary DNS server copies domain information from another DNS server, called the master server. It can also act as a backup name server for clients when the primary server is unreachable. The domain name is assumed to be fully qualified whether or not it ends in a trailing period. Example: horror.cartoon.net. |
Master DNS Servers' Host Addresses |
The host addresses of the master DNS name servers in the order in which they should be queried. A master DNS server can be either an existing primary or secondary DNS server. Example: 118.144.102.6 |
From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.
Choose one of the following:
To modify a DNS secondary domain, click Modify, and make the changes in the form using the information in Table 3-10.
To delete a DNS secondary domain, click Delete, and then confirm the operation.
If you edit the DNS files manually as well as using the Netra DNS Server configuration component, the following information explains what changes Netra makes. You do not have to read this section if you always use Netra to configure DNS.
The "Modify the DNS Server Configuration" form edits the "local" file (the file with the reverse lookup for the local machine) and depending on the type of DNS server, either the "cache" file or the "root" file. If you change the name of the domain in which the server resides or the DNS administrator, all the primary resource files are rewritten to create a new SOA record and to update the name server record.
If you modify a primary domain, the corresponding resource file and the entry in the named boot file are rewritten.
If you modify a primary domain, only the entry in the named boot file is rewritten.
When recreating resource files, Netra does not change the values in the SOA (other than the revision number). Resource Records of other types than those that can be entered on the forms are left intact. TTLs from individual resource records that are edited by Netra are removed.