test

Netra j 3.0 Administrator's Guide

Chapter 3 Using Network Services

This chapter describes some of the Network Services Administration modules:

Anonymous FTP Administration

The Internet File Transfer Protocol (FTP) enables you to copy files from one computer to another over a network. You run an FTP client program on one computer and it connects to the FTP server program running on the other.

To use FTP, you must have a valid login account on the computer with the FTP server, unless the server is set up to accept anonymous FTP. An anonymous FTP server enables users without local accounts to access a specially designated FTP directory. From this directory, they can copy files to the computer running the FTP client ("downloading files"). Optionally, users can also be allowed to copy files into a subdirectory of the FTP directory ("uploading files").

The Anonymous FTP module enables you to configure your server in one of three states:

By default, Netra j designates /export/ftp as the anonymous FTP directory. However, if you have installed Netra on top of an existing configuration, any changes you make to the anonymous FTP configuration preserve the current directory setup.

To Configure Anonymous FTP

  1. From the Main Administration page, under "Network Service Administration," click Anonymous FTP.

    The Anonymous FTP Administration page is displayed with the current state of the server.

  2. Complete the form using the information in the following table.

    Table 3-1 Anonymous FTP Information

    Option 

    Description 

    Enable anonymous FTP with upload and download capability  

    Users without accounts on the Netra server can connect to the Netra server using FTP. The anonymous FTP account has a directory called /pub that contains files available for downloading, and a directory called/incoming into which users can upload files.

    Enable anonymous FTP with download capability only 

    Users without accounts on the Netra Server can connect to the Netra server using FTP. The anonymous FTP account has a directory called /pub that contains files available for downloading. Users cannot copy (upload) files into the directory /incoming.

    Disable anonymous FTP 

    Only users with valid accounts on the Netra server can connect to it using FTP. 

  3. Place all files that are to be available through FTP in the /export/ftp/pub directory (if you are using the default Netra setup).

    Anonymous FTP users see this directory as /pub. If the server is configured with upload capability, anonymous users are able to copy files to the /export/ftp/incoming directory. FTP users see this directory as /incoming.

Mail Administration

This section describes how to use Mail Administration module.

If a server is configured to provide mail services, it becomes a mail server (a mail gateway between clients on the LAN and the Internet) and a mail host (incoming mail to users is available in the directory /var/mail). The Netra server runs both IMAP4 and POP3 daemons.

Note -

The server can be a mailhost / mail server without being configured as such from Netra j. In that case, the module says "Netra mail services are inactive." It says that about any configuration except one created by Netra i 3.2 or Netra j 2.0 or 2.0.1.

You can use Netra j to set the following aspects of the mail server configuration.

The choices made when activating the mail services can be changed at a later time. If the Mail Administration page is loaded when Netra mail services are active, the following links: "Modify the mail services" and "Disable the Netra mail services configuration" are displayed. The first link shows the same form as for the initial configuration, while the latter link restores the mail services to the state they were in before Netra mail services were activated.

Mail Directories

The first choice concerns where users' incoming mail is kept. To users, the mailboxes appear to be in the directory /var/mail, but if space on the relevant disk partition is limited, you may prefer for /var/mail to be a link to another directory. Earlier versions of Netra (Netra j 1.0 or Netra i 3.1) linked /var/mail to /export/mail. The form shows whether /var/mail is currently linked to another directory, and gives the option of either keeping the mail in /var/mail or to link it.

If the location of the mailboxes changes, the mailboxes are moved to the new location from the current mail directory unless the /var/mail directory was mounted onto the Netra server from another server. In the latter case, the remote directory is unmounted without moving the mailboxes.

Directory Sharing

The second choice concerns whether the mailbox directory should be shared so that it can be mounted onto other computers. If the directory is to be shared, other computers can mount the Netra server's /var/mail directory so that it appears to be part of their own file system. (The directory /var/mail can be mounted as such even if it is actually linked to another directory.)

Mail Return Address Path Format

The third choice determines the format of the return address on outgoing mail, which can be either user@host.domain or user@domain. For example, suppose the Netra server's host name is stimpy and that stimpy resides in the domain cartoon.net. With the user@host.domain format, mail from the user setup goes out as from the sender setup@stimpy.cartoon.net, while with the user@domain format it is setup@cartoon.net.

The return address is used when people reply to messages sent out by the Netra server. For mail using the user@domain format to find its way back, the DNS server needs to know what server(s) deal with mail on the domain. This is accomplished by adding an MX record to the DNS database. If the Netra server is acting as the primary domain name server for the domain in which the server resides, this can be done through the Name Services module (See "Name Service Administration "). With reference to the example above, you would modify the domain cartoon.net by making an entry in the Mail Addresses/Preferences/Mail Servers box; in this case the mail address would be cartoon.net, the preference can be 5, and the mail server stimpy.cartoon.net.

To Configure a Server to Provide Mail Services

  1. From the Main Administration page, under "Network Service Administration," click Mail, then click Configure this server as mailhost and a mailserver.

    The Configure Mail Services Administration page is displayed.

  2. Complete the form using the information in the following table.

    Table 3-2 Mail Administration

    Option 

    Description 

    Store Mail in /var/mail

     

    Store mail in /var/mail directory

    Link /var/mail to directory

    Link /var/mail to the directory specified in the textbox and store the mail in that directory.

    Do you want the mail directory to be shared? 

    Determine whether other computers can mount the mailbox directory. Select yes or no. 

    Mail return address path format is: user@host.domain

    The return address on mail includes the host name of the Netra server. 

    Mail return address path format is: user@domain

    The return address on mail does not include the host name of the Netra server. For the mail format of user@domain to be used, the DNS primary server must have a mail exchanger record (MX record) for the Netra server in its database.

To Modify Mail Services

  1. From the Main Administration page, under "Network Service Administration," click Mail, then click Modify the mail services.

    The Modify Mail Services Administration page is displayed.

  2. Complete the form using the information in Table 3-2.

To Disable Netra Mail Services

  1. From the Main Administration page, under "Network Service Administration," click Mail, then click Unconfigure the mail services configuration.

    The Unconfigure Mail Services Administration page is displayed.

  2. Click OK to confirm the operation.

    This restores the mail configuration to what it was before being configured by Netra j.

Mail Alias Administration

The Netra Mail Administration module enables you to add and modify aliases that mail a copy of a message sent to the name to one or more users. Typically, such aliases are used to distribute messages to an interest group or to redirect a single users' mail, either because their mail should go to another server, or because they receive mail under an alternate name. Mail aliases that map names to a group of recipients are called as mailing lists, while mail aliases that map a name to a single user are called alias names.

In addition to creating new aliases, the mail administration module also allows you to modify two important system aliases: root and postmaster. These are standard names that people use for convenience: if you do not know who is in charge of a system, you use root to reach the systems administrator, and postmaster to reach the person who administers mail. Note that although root is a valid user, mail to root should always be redirected to a regular user (previous versions of the Netra software had a special form to administer the system administrator alias).

Mailing Lists

An example of how you might use a mailing list is to send messages to members of a volleyball team. You could create an alias with the name "vball" that has the email addresses of all the team members as the recipients. This way, mail sent to "vball" reaches the whole team without the sender needing to know the members' individual addresses (or even exactly who is on the team at any given point). When a member leaves or a new member joins, you update the alias.

Alias Names

Alias names redirect mail to single users. For instance, the user Tom Jones with user name "tom" may want to receive mail as "tjones". In this case, you would add an alias with the name "tjones" and the single recipient "tom." If John Smith, with user name "john," has left and wants to receive mail at his new address of jsmith at "otherdomain," add an alias that maps "john" to "jsmith@otherdomain."

To Modify the System and Mail Administrator Aliases

  1. From the Main Administration page, under "Network Service Administration," click Mail.

    The Mail Administration page is displayed.

  2. Click Modify either System Administrator alias or Mail Administrator alias.

  3. Enter the mail addresses of the alias members (see the following table).

    Table 3-3 System Administrator Alias Administration

    Option 

    Description 

    Alias Members 

    A list of people, one per line, who receive mail sent to root or postmaster. Each line must be a valid email address.

    Note -

    If the Netra software has been installed onto a server that mounts /var/mail from a remote server, mail is handled by the remote server. This situation requires that the members of the administrator aliases are valid mail addresses on the remote server.

  4. Click OK.

Configuring Aliases

To Create a Mail Alias

  1. From the Main Administration page, under "Network Service Administration," click Mail, then click Add a mail alias.

    The Add A Mail Alias page is displayed.

  2. Type the information in the form using the following table.

    Table 3-4 Information for Mail Alias Administration

    Option 

    Description 

    Alias Name 

    The name of the mail alias. A copy of all mail sent to the alias is sent to each member of the alias. Alias names: 

    o Must be at least one character and no more than 20 characters 

    o Must begin with a letter, and can include letters, digits, hyphens, underscores, and periods 

    o Are case insensitive 

    o Must be unique  

    Alias Members 

    A list of people, one per line, who receive mail sent to the alias. Each line must be a valid email address.  

     

    There is a limit on the size of the entry made to the system (the entries together with comma separators must not exceed 1000 characters). Netra issues a warning if your alias exceeds this limit. You can use nested aliases to circumvent this restriction.  

    Note -

    You can use Netra to administer only aliases whose member list is other users specified in the alias file. You cannot administer aliases that send mail to programs or to files.

To Modify or Delete a Mail Alias

  1. From the Main Administration page, under "Network Service Administration," click Mail.

    The Mail Administration page is displayed.

  2. Choose one of the following options:

    • To modify an existing alias, click Modify for the required alias and make the changes in the form using Table 3-4.

    • To delete an alias, select an alias, click Delete to remove the alias, and then confirm the operation.

Mail Log File

Log files should be viewed and cleared periodically.

To View or Clear the Mail Log

  1. From the Main Administration page, under "Network Service Administration," click Mail.

    The Mail Administration page is displayed.

  2. Choose View or Clear the Mail log.

    • Click View; the Mail Server Log File is displayed.

    • Click Clear, then confirm the operation to flush the file.

Name Service Administration

Every machine on a network must have a unique identifier to distinguish itself from other machines on the network. This is also true for all machines on the Internet. Thus, every machine is given a host address. This is also referred to as the IP address. A host address has the form 115.144.79.5, where each of the four numbers separated by periods can be in the range of 0 to 255. Such addresses are difficult to memorize, so each machine is also given a host name that is associated with its host address. Users generally use a host name, such as stimpy.comedy.cartoon.net, to access a specific machine on a given network.

The process by which a host name is associated with or translated to its host address is called name resolution. It is usually performed by a name service.

The Name Services module enables you to do the following:

Name Services on the Netra Server

The Netra server provides three types of name services:

The Netra server can use any or all of the name services at the same time. If you decide to use more than one name service, the default order configured by Netra j is NIS, local, DNS.

For example, suppose your Netra server is configured to use the local name service and DNS. When a name service query is made, the server attempts name resolution by looking up the host name in the local database first. If the host name is found, the server returns the host address. If not, the query is passed to a DNS server. If the DNS server resolves the query, it returns the information.

Correct Hosts Policy for /etc/nsswitch.conf

The name service configuration file, /etc/nsswitch.conf, should not be configured to only search the NIS database for host information. The search should include a files option to search in the local files.

For example, the name service ignores information in the local host if the /etc/nsswitch.conf file contains the following entry: 

hosts: nis [NOTFOUND=return] dns

For the Netra j server and the NC clients to work correctly, change the /etc/nsswitch.conf file to include one of the following entries: 

files nis [NOTFOUND=return] dns

or 

nis files dns

Configuration Options

The four name service options (local, NIS, DNS server/client, and DNS client) work independently of each other.

Local Name Service

The local name service provides a local database that associates the names of hosts with their host addresses. This name service is only available to programs running on the Netra server.

For the local name service, the Netra server is both client and server. As a local name server, your Netra server contains a list of host-name-to-host-address mappings for its own use. These mappings are available only to applications running on the Netra server. Information entered in the local database is automatically available to programs running locally.

If the Netra server is configured as a NIS master, the Local Host information is pushed to the hosts NIS map.

To Configure Local Name Services

  1. From the Main Administration page, under "Network Service Administration," click Name Service, then click Local Name Service.

    The Local Name Server Administration page is displayed.

  2. Complete the form using the information in the following table.

    Table 3-5 Local Name Server Administration

    Host Information 

    Description 

    Host Addresses/ Host Names/ Aliases 

    The host addresses and corresponding host names and aliases. The host names can be partially or fully qualified to be compatible with other name services. However, this database resolves only host names that have an exact match in the database. Maximum 2000 records. 

NIS

The network information service (NIS) provides name services and other information, such as users on the network, for a local network. If there is a NIS server on the network, use the Netra Name Service module to configure the Netra server as a NIS client. This means that it uses NIS to resolve host names, host addresses, and host aliases.

The Netra j software provides NIS client/slave/master capability. The following maps are specifically required by NCs: passwd.byname, passwd.byuid, printers.conf.byname, auto.home,hosts, and bootparms.

To Configure NIS for the Netra Server

  1. From the Main Administration page, under "Network Service Administration," click Name Service, then click NIS (Network Information Name Service).

    The NIS Administration page is displayed.

  2. Click Configure.

    The NIS Configuration page is displayed.

  3. Complete the form using the information in the following table.

    Table 3-6 NIS Configuration

    NIS Domain 

    Description 

    NIS Domain Name 

    The NIS domain in which the Netra server resides. 

    NIS Client 

    Select this option to be a NIS client only. A NIS server for this domain must exist on the same subnet as the Netra server. 

    NIS Master Server 

    Select this option to provide NIS information to other NIS clients. The Netra administration provides only the following maps: auto.home, passwd.byname, passwd.byuid, printers.conf.byname, auto.master, hosts, bootparms and ypservers.

    NIS Slave Server 

    Select this option to provide NIS information to other NIS clients when there is no other NIS server on your subnet. The NIS maps must exist on a different server (the NIS master server) and must be transferred to the Netra server. If this option is selected, all maps are transferred from the master server immediately.  

    Map Master 

    The host name or host address of the NIS master server. This field is relevant only for slave servers.  

To Modify or Unconfigure NIS Configuration
Note -

The Modify and Unconfigure options are displayed only when the Netra server is configured.

  1. From the Main Administration page, under "Network Service Administration," click Name Service, then click NIS (Network Information Name Service).

    The NIS Administration page is displayed.

  2. Choose one of the following:

    • To modify NIS configuration, click Modify, update the form using the information in Table 3-6, and click OK to confirm the operation.

    • To unconfigure an NIS configuration, click Delete NIS Configuration, and confirm the operation. The Netra server no longer uses NIS to resolve host names, and the NIS domain name is ignored.

DNS

The Domain Name System is the name resolution system used by the Internet. It is a hierarchical naming system based on the concept of domains. At the top level, there is the domain . (the root domain), below it are domains such as com, edu, or ie, which act as a first partition of the name space. Individual organizations have their own domains below these domains. Below com you find companies in the US (for example, sun.com), below edu are American educational institutions (for example, stanford.edu), and below ie you find institutions in Ireland (for example, tcd.ie). The individual organizations often divide these domains into subdomains.

DNS works by delegation. Each domain is served by one or more DNS servers, which has a database of the hosts in the domain. In addition, the DNS servers also have a list of other DNS servers to query in case they cannot resolve a name locally. This list typically consists of a set of DNS servers called root servers at the top of the DNS hierarchy, which in turn know what DNS servers hold data about the different top-level domains.

Individual hosts use the Domain Name System to resolve name queries by becoming DNS clients. To configure a DNS client, you specify the IP address of the DNS server that you want to respond to the queries for you. You have to do this even if the individual host is a DNS server, in which case you typically set it to answer the queries itself.

The hostname of a computer together with its full domain name (ending in the top level domain) makes up its complete DNS name. If the host stimpy resides in a domain called comedy, which is a subdomain of cartoon under the top level domain net, then stimpy.comedy.cartoon.net is the complete name for stimpy.

An important distinction used in the text below is that between a fully qualified name or a partially qualified name. When referring to the fully qualified name of a host of a domain, it means the complete DNS name ending in a trailing period. The fully qualified name for stimpy is stimpy.comedy.cartoon.net..

A partially qualified name is a name that does not specify the domain branch all the way up to the top. Partially qualified names are used as a shorthand when the name resolution software can attach the rest of the domain name. If you are in the domain comedy.cartoon.net and use stimpy to mean stimpy.comedy.cartoon.net, then you are using a partially qualified name. If a DNS name does not end with a trailing period, it is treated as partially qualified.

The distinction between fully and partially qualified names is important in many of the DNS configuration tasks - if you experience any problems, please refer to the help pages, which always tell you which one to use.

DNS Server Options

There are several different types of a DNS server. At the most basic, the server does not hold any permanent data about any domains itself, but simply forwards queries to other servers (a cache-only server) and stores the result. A DNS primary server has a master database for a domain. A DNS secondary server provides a local copy of master database for a domain that it copies from a primary server. DNS server can be both a primary and a secondary domain server at the same time.

All DNS servers store the results of successful queries (whether it resolved the query itself or forwarded it to another DNS server). If the server receives another query for the same name, it replies with the stored answer. This is called caching. A server that only does this (a cache-only server) can be useful to shorten the response time compared with contacting a more remote DNS server.

There are two different ways in which a DNS server can provide data for a domain; it can be a primary, or a secondary server for the domain. For the primary server, the DNS administrator maintains the master database for the hosts in the domain on the server. For the secondary server, the server keeps a local copy of the master database for the domain that it retrieves from the primary server. It periodically compares its database to the one on the primary server and requests a new copy if a difference is detected.

The difference between normal caching and being a secondary server for a domain is that normal caching only stores the results from previous queries. A secondary server actively retrieves the information in anticipation of future requests. This reduces the load on the primary server, and also makes it a backup in case the primary server cannot be contacted. If your server is a primary server for a domain, you should have a secondary as a backup.

There are two different types of DNS server configuration that you use depending on what the structure of your local domain is. The first type, which is referred to as Basic DNS Server, involves specifying a list of other DNS servers to query if a name cannot be resolved locally. The second type is called a DNS Internal Root Server. It is used on Intranets without an Internet connection (in other words, without access to any other DNS servers), and also on large Intranets with several subdomains, where there is a need for special DNS servers for the internal hierarchy.

Finally, a DNS Primary Server may need to provide reverse maps (IP address to name) as well as forward maps (name to IP address). Please consult with your ISP to find out whether this responsibility is delegated to you or not.

Configuring the DNS Server

Basic DNS Server

To Configure a Basic DNS Server

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.

  1. From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.

  2. Under "DNS Server," click Configure as a basic DNS Server.

    The Basic DNS Server Configuration page is displayed.

  3. Complete the form using the information in following table.

    Table 3-7 Basic DNS Server Configuration

    Option 

    Description 

    DNS Domain Name 

    The DNS domain in which the Netra server resides. This name is used for two purposes:  

    • as a contact address for the DNS administrator.

    • when creating the DNS server record for this server for any primary domains for which it is responsible.

    The domain name is assumed to be fully-qualified whether or not you enter a period at the end. Example: comedy.cartoon.net.

    DNS administrator's user name  

    Enter the name or alias of the local user (for example, root) who is responsible for DNS. All DNS database files contain a contact address - the address for this server consists of the name of this user, the name of the Netra server, and the domain name entered into the domain field.

    Root Name Servers/ IP Address 

    The fully qualified host names and host addresses of a set of DNS servers to contact to resolve name service queries. Use the default servers if the Netra server is connected directly to the internet. If the Netra server is behind a firewall, enter a set of servers that it can reach. 

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.

Note -

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.

To Modify or Delete a Basic DNS Server

  1. 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.

  2. 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.

DNS Internal Root Server

To Configure a DNS Internal Root Server

  1. From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.

  2. Under "DNS Server," click Configure as a internal root server).

    The Configure as an Internal DNS Root Server page is displayed.

  3. Complete the form using the information in following table.

    Table 3-8 DNS Internal Root Server Configuration

    Option  

    Description 

    DNS Domain Name 

    The DNS domain in which the Netra server resides. This name is used for two purposes:  

    • as a contact address for the DNS administrator.

    • when creating the DNS server record for this server for any primary domains for which it is responsible.

    The domain name is assumed to be fully-qualified whether or not you enter a period at the end. Example: cartoon.net.

    DNS administrator's user name  

    Enter the name or alias of the local user (for example, root) who is responsible for DNS. All DNS database files contain a contact address - the address for this server consists of the name of this user, the name of the Netra server, and the domain name entered into the domain field.

    Internal Root Server / IP Address 

    This field is only relevant if the internal network has other DNS internal root servers (an entry for this server is created automatically). If there are none, leave this field blank. Enter the fully qualified host names and host addresses of each DNS internal root server. 

    DNS Server / IP Address  

    This field is only relevant if the internal network has non-root DNS servers that reside in the top-level domain and to which this server delegates responsibility for primary domains. If there are none, leave this field blank. Enter the fully qualified host names and host addresses of each DNS server. If a server has more than one IP address, create an entry for each address 

    in-addr.arpa Domain Name / DNS Server 

    This field is only relevant if this root server delegates responsibility for reverse maps (in-addr.arpa domains) to other DNS servers on the internal network. If it does not, leave this field blank. Create domain name/name server entries for the in-addr.arpa domains maintained on the other DNS servers. Use fully qualified names in both cases. 

    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.

Note -

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.

To Modify or Delete a DNS Internal Root Server

  1. 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.

  2. 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.

DNS Primary Server

To Configure the Netra Server as a DNS Primary Server

  1. From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.

  2. Under "DNS Server," click Add a primary domain.

    The Add DNS Primary Domain page is displayed.

  3. 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). 

  4. 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.

To Modify or Delete a DNS Primary Domain

  1. 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.

  2. 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.

Example of a Primary Domain Configuration

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.

Automatic Reverse Map Generation

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.

To Generate Reverse Maps

  1. From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.

  2. Under "DNS Server," click Enable Automatic Reverse Map Generation.

    The DNS Reverse Map Generation page is displayed.

  3. Click OK.

To Disable Automatic Reverse Map Generation

  1. From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.

  2. Under "DNS Server," click Disable Automatic Reverse Map Generation.

    The DNS Reverse Map Generation page is displayed.

  3. 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.

  4. Click OK.

DNS Secondary Domain

To Configure the Netra Server as a DNS Secondary Server

  1. From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.

  2. Under "DNS Server," click Add a secondary domain.

    The Add DNS Secondary Domain page is displayed.

  3. 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

To Modify or Delete a DNS Secondary Domain

  1. From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Server Administration.

  2. 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.

Notes to Those Who Also Administer DNS Manually

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.

Configuring the DNS Client

To Configure the Netra Server as a DNS Client

  1. From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Client Administration.

    The DNS Client Administration page is displayed.

  2. Click Configure as a DNS Client.

    The DNS Client Administration page is displayed.

  3. Complete the form using the information in the following table.

    Table 3-11 DNS Client Administration

    Option 

    Description 

    DNS Domain Name 

    The DNS domain that is appended to qualified host names. Usually, this is the name of the domain in which the Netra server resides. Example: comedy.cartoon.net

    Name Server 1  

    The host address of the DNS server that is tried first for all DNS queries. Example: 118.144.79.5

    Name Server 2 (optional) 

    The host address of the DNS server to use, if the first name server is unreachable. Example: 118.144.79.6

    Name Server 3 (optional) 

    The host address of the DNS server to use, if the first two name servers are unreachable. Example: 118.144.102.6

If the Netra server is configured to be a DNS server and is to be a client of itself, then set Name Server 1 to be 127.0.0.1 (the loopback address).

To Modify or Delete DNS Client Setup

  1. From the Main Administration page, under "Network Service Administration," click Name Service, then click DNS (Domain Name Service) Client Administration.

    The DNS Client Administration page is displayed.

  2. Choose one of the following:

    • To modify a DNS client setup, click Modify, and make the changes in the form using Table 3-11 as a reference.

    • To delete a DNS client setup, click Delete then confirm the operation.

Sun WebServer Administration

To Access Sun WebServer Administration

  1. From the Main Administration page, under "Network Service Administration," click Sun WebServer (port 80).

    The Sun WebServer Administration page is displayed.

  2. Login.

    The Sun WebServer console is displayed.

  3. See the Sun WebServer online help for administration procedures.