Cisco Cisco Content Security Management Appliance M160 Guía Del Usuario
14-38
AsyncOS 9.0 for Cisco Content Security Management Appliances User Guide
Chapter 14 Common Administrative Tasks
Changing Network Settings
DNS Alert
Occasionally, an alert may be generated with the message “Failed to bootstrap the DNS cache” when an
appliance is rebooted. The message means that the system was unable to contact its primary DNS
servers, which can happen at boot time if the DNS subsystem comes online before network connectivity
is established. If this message appears at other times, it could indicate network issues or that the DNS
configuration is not pointing to a valid server.
appliance is rebooted. The message means that the system was unable to contact its primary DNS
servers, which can happen at boot time if the DNS subsystem comes online before network connectivity
is established. If this message appears at other times, it could indicate network issues or that the DNS
configuration is not pointing to a valid server.
Clearing the DNS Cache
The Clear Cache button from the GUI, or the d
nsflush
command (for more information about the
dnsflush
command, see the CLI Reference Guide, available from the location specified in
), clears all information in the DNS cache. You may choose to use this feature
when changes have been made to your local DNS system. The command takes place immediately and
may cause a temporary performance degradation while the cache is repopulated.
may cause a temporary performance degradation while the cache is repopulated.
Configuring DNS Settings
via the Graphical User Interface
Procedure
Step 1
On the Management Appliance > Network > DNS page, click the Edit Settings button.
Step 2
Select whether to use the Internet’s root DNS servers or your own internal DNS server(s), and specify
authoritative DNS servers.
authoritative DNS servers.
Step 3
If you want to use your own DNS server(s) or specify authoritative DNS servers, enter the server ID and
click Add Row. Repeat this for each server. When entering your own DNS servers, specify a priority as
well. For more information, see
click Add Row. Repeat this for each server. When entering your own DNS servers, specify a priority as
well. For more information, see
.
Step 4
Choose an interface for DNS traffic.
Step 5
Enter the number of seconds to wait before canceling a reverse DNS lookup.
Step 6
Optionally, clear the DNS cache by clicking Clear Cache.
Step 7
Submit and commit your changes.
Configuring TCP/IP Traffic Routes
Some network environments require the use of traffic routes other than the standard default gateway. You
can manage static routes in the GUI through the Management Appliance > Network > Routing page, or
in the CLI by using the
can manage static routes in the GUI through the Management Appliance > Network > Routing page, or
in the CLI by using the
routeconfig
command.
•
•
Managing Static Routes in the GUI
You can create, edit, or delete static routes by using the Management Appliance > Network > Routing
page. You can also modify the default gateway from this page.
page. You can also modify the default gateway from this page.