The configuration file config/webui.conf
in the NameSurfer directory tree contains
a number of configurable settings in a simple, human-readable text
format. It is read by the the NameSurfer HTTP server process on startup. Changes made to this file will not take effect
until the process is killed and restarted.
Each setting is entered on a line of its own as a "name: value" pair.
Empty lines and comments beginning with a # character are allowed.
The following settings are supported:
A soft limit on the maximum number of simultaneous
child processes that may be spawned by the NameSurfer daemon.
Additional child processes may be created in excess of this limit, but
their creation will be delayed in order to limit server load.
The name of the host this NameSurfer is running on. This should
be identical to the hostname part of the URL by which users connect to
the NameSurfer WWW user interface. This is used by the WWW user
interface when issuing HTTP redirects pointing back to the server
itself. With certain (broken) WWW browsers, such redirects have to
contain an absolute URL, making knowledge of the hostname necessary.
If no value is specified, NameSurfer will attempt to determine the
hostname by running the operating system's "hostname" command.
If the server's idea of the hostname differs from that of the user,
certain WWW browsers may display an additional authentication dialog
after the first HTTP form submission in each NameSurfer session.
When true, the WWW user interface will display MX, HINFO,
and RP data in the form of HTML selectors with predefined
choices based on the current zone contents.
The selector display requires NameSurfer to generate special summary
information from the zone data on startup. This may take a
substantial amount of time and memory if the amount of data is large.
We recommend setting fancy_selectors to "false" if your
DNS data totals more than 2000 resource records, or if you are
experiencing problems with excessive startup time.
When true, the zone page will use contrasting background
colors for alternate lines.
Please note: this applies only to FusionLayer NameSurfer versions 7.1.1 and earlier.
When true, enable optional JavaScript features of the user interface.
Currently, there is only one such feature: when the zone display or
the index display is divided into multiple pages, positioning the
mouse cursor over a page number shortcut will cause the first and last
domain name on that page to be displayed in the window footer of
compatible Web browsers.
When false, HTML cookies will not be used in NameSurfer. When cookies
are not used, NameSurfer will always return to the index page
after help pages have been browsed. When true, NameSurfer will
use HTML cookies.
The IP address of a name server providing recursive name service,
e.g., a BIND server. This is needed to automatically look up
the authoritative servers when loading data by zone transfer.
When true, searching on the index page works for all the zones, and might
be very slow. Othervise searching on the index page works only for domain
names.
The host name or numeric IP address of the machine running
the NameSurfer server. Usually this is the same machine
as the one running the user interface, so the loopback
address 127.0.0.1 may be used.
The port number where the NameSurfer server listens for DNS queries.
Used by the user interface to send queries and updates.
Should be the same as the dns_port configuration option of the server.
This option controls how NameSurfer updates reverse map PTR records.
If it is set to 'true', when doing update all the existing PTR records
for the reverse zone node are removed and replaced with a single
new PTR record. Default is 'false'.
If this option is enabled, NameSurfer web UI will use one of the available external
authentication methods for checking user credentials instead of the internally stored password.
Detailed configuration for the external authentication is in the
authentication.conf configuration file.
The IP address of this host (the host on which FusionLayer NameSurfer primary name server
runs). This address is used by BIND Configuration as the master ip address.
This option enables more strict security policy for FusionLayer NameSurfer which enables that account
will be disabled after 5 failed login attempts. Also when creating or modifying passwords, passwords
are checked against dictionary files.
If session login is in use, invalidate inactive sessions after the specified time (seconds) of
inactivity. If session login is not used, clear current noon-login session cookie data after the inactivity period has passed.