Policy Framework Configuration Guide - Juniper Networks

Junos 10.4 Policy Framework Configuration Guide
To disable recognition of DNS or TFTP requests on one or more interfaces, include the
no-listen statement. If you do not specify at least one interface with this statement, the
forwarding service is global to all interfaces on the router or switch.
The following sections discuss the following:
• Tracing BOOTP, DNS, and TFTP Forwarding Operations on page 372
• Example: Configuring DNS Packet Forwarding on page 374
Tracing BOOTP, DNS, and TFTP Forwarding Operations
BOOTP, DNS, and TFTP forwarding tracing operations track all BOOTP, DNS, and TFTP
operations and record them in a log file. The logged error descriptions provide detailed
information to help you solve problems faster.
By default, nothing is traced. If you include the traceoptions statement at the [edit
forwarding-options helpers] hierarchy level, the default tracing behavior is the following:
• Important events are logged in a file called fud located in the /var/log directory.
• When the file fud reaches 128 kilobytes (KB), it is renamed fud.0, then fud.1, and so on,
until there are 3 trace files. Then the oldest trace file (fud.2) is overwritten. (For more
information about how log files are created, see the Junos OS System Log Messages
Reference.)
• Log files can be accessed only by the user who configures the tracing operation.
You cannot change the directory (/var/log) in which trace files are located. However,
you can customize the other trace file settings by including the following statements at
the [edit forwarding-options helpers] hierarchy level:
[edit forwarding-options helpers]
traceoptions {
file filename ;
flag {
address;
all;
config;
domain;
ifdb;
io;
main;
port;
rtsock;
tftp;
trace;
ui;
util;
}
level severity-level;
no-remote-trace;
}
372
Copyright © 2010, Juniper Networks, Inc.