The First-Time Boot utility prompts you to define a password that allows remote access to the 3DNS Controller, and also prompts you to define a password for the 3DNS Web server. You can change these passwords at any time.
You can create new users for the 3DNS Web server, change a password for an existing user, or recreate the password file altogether, without actually going through the 3DNS Web server configuration process:
This starts the 3dns_web_passwd script, which lets you provide access to the 3DNS Web Administration site for selected users only, and assigns passwords for those users. If you don't use this script, all users have access to the Web Administration site.
You can configure the 3DNS Controller to allow electronic mail to be sent from the system. This configuration must be completed if the 3DNS Controller is to send electronic mail to the administration workstation or to an alphanumeric pager. The 3DNS platform includes an example configuration file that is suitable for most sites. Before you use this configuration file, however, you do have to customize it for your network environment.
When you customize this file, you enter the name of the mail relay server.
3dns: /etc# nslookup
The information returned includes the name of the mail exchanger.
0,15,30,45 * * * * root /usr/sbin/sendmail -q > /dev/null 2>&1
Including this line in the /etc/crontab file sets Sendmail to flush the outgoing message queue for any email that could not be delivered immediately. Because the 3DNS Controller does not accept email from external sources, there is no need to run the Sendmail daemon. Queue flushes are issued via crontab.
Because the 3DNS Controller does not accept local email, bounces or undelivered messages go unnoticed. This requires that the administrator is notified when a message is bounced or undelivered.
The 3DNS platform includes the GateD daemon, which is disabled by default. To enable the 3DNS Controller to accept dynamic routing updates from your routers, you must first create the appropriate configuration file, /etc/gated.conf.
You enable the GateD daemon on the 3DNS Controller by typing the following at the command line prompt:
Next, you need to edit the /etc/netstart file and change the definition of the gated variable as shown below:
The 3DNS Controller is now configured to accept dynamic route updates from your router.
Note: Certain network environments may require that you modify the routing tables or your router. If you have communication problems between your router and the 3DNS Controller, please contact Technical Support at F5 Networks, Inc.