Applies To:Show Versions
3-DNS Controller versions 1.x - 4.x
- 4.0.1 PTF-04, 4.0.1 PTF-03, 4.0.1 PTF-02, 4.0.1 PTF-01, 4.0.1
Additional Setup Options
- Enabling remote login tools
- Preparing workstations for command line access
- Using a serial terminal
- Configuring Sendmail
If you are setting up a crypto 3-DNS Controller that needs to communicate with non-crypto 3-DNS Controllers, you must enable the rsh and rcp tools on the crypto 3-DNS Controller. These are the standard communication and copying tools that non-crypto 3-DNS Controllers, BIG-IP Controllers, and EDGE-FX Caches use.
To enable RSH on a crypto 3-DNS Controller
Run the config_rshd script from the command line utility. The config_rshd script performs several essential steps to enable access for rsh and rcp. We strongly recommend that you use the script rather than doing this manually.
The type of system you have determines the options you have for remote command line administration:
- Crypto 3-DNS Controllers support secure shell (SSH) command line access. If you have a Windows-based PC workstation, you can use the Mindbright Mindterm SSH client to run an ssh session. If you have a UNIX workstation, you can use a standard ssh client.
- Non-crypto 3-DNS Controllers support command line access using a standard rsh shell.
If you are working with a crypto 3-DNS Controller, you can access the Mindterm SSH client through the web-based Configuration utility.
If you want to use a serial terminal (in addition to a standard console) with the 3-DNS Controller, you need only ensure that the serial terminal settings are as follows:
- 9600 baud
- 8 bits
- 1 stop bit
- No parity
You can configure the 3-DNS Controller to send email notifications to you, or to other administrators, using the Sendmail utility. The 3-DNS Controller includes a sample Sendmail configuration file that you can use to start with, but you must customize the Sendmail setup for your network environment before you can use it.
Before you begin setting up Sendmail, you may need to look up the name of the mail exchanger for your domain. If you already know the name of the mail exchanger, refer to Setting up Sendmail, on page 4-3 , for details about setting up the sendmail daemon itself.
You can use the nslookup command on any workstation that is configured for lookup. Once you find the primary IP address for your domain, you can find the mail exchanger for your domain.
To find the mail exchanger for your domain
- Identify the default server name for your domain. From a workstation capable of name resolution, type the following on the command line:
- The command returns a default server name and corresponding IP address:
Default Server: <server name>
- Use the domain name to query for the mail exchanger:
The returned information includes the name of the mail exchanger. For example, the sample information shown in Figure 4.1 lists bigip.net as the preferred mail exchanger.
bigip.net preference = 10, mail exchanger = mail.domain.com
bigip.net nameserver = ns1.bigip.net
bigip.net nameserver = ns2.bigip.net
bigip.net internet address = 192.168.112.1
ns1.bigip.net internet address = 192.168.112.2
ns2.bigip.net internet address = 192.168.112.3
When you set up Sendmail, you must edit three configuration files. Since the 3-DNS Controller does not accept email messages, you can use the crontab utility to purge unsent or returned messages and send them to yourself or another administrator.
To set up and start Sendmail
- From the command line, open the /etc/rc.conf file. Add the following line to the file:
- Save and close the /etc/rc.conf file.
- To set the name of your mail exchange server, open the /etc/mail/sendmail.cf file and set the DS variable to the name of your mail exchanger. The syntax for this entry is:
- Save and close the /etc/mail/sendmail.cf file.
- To allow Sendmail to purge outgoing messages that cannot be delivered immediately from the queue containing mail, open the /etc/crontab file, and change the last line of the file to read:
0,15,30,45 * * * * root /usr/sbin/sendmail -q > /dev/null 2>&1
- Save and close the /etc/crontab file.
- To prevent returned or undeliverable email from going unnoticed, open the /etc/aliases file and create an entry so that root points to you or another administrator at your site.
- Save and close the /etc/aliases file.
- Run the /usr/sbin/newaliases command to generate a new aliases database that incorporates the information you added to the /etc/aliases file.
- To turn Sendmail on, either reboot the system, or type the following command:
/usr/sbin/sendmail -bd -q30m