On the DNS index page you can select one of several
zones for editing. You can also perform
some other operations that apply to FusionLayer NameSurfer as a whole, rather
than to a specific zone.
The index page contains the following functions (some may be missing,
depending on user permissions and licensing options):
This section lists the zones currently maintained using this FusionLayer
NameSurfer. Each zone name is a link to the
zone page
for that zone. These are the "forward" mappings. The corresponding
reverse mappings are listed separately in the "Reverse zones" section.
This section lists all the IN-ADDR.ARPA and IP6.ARPA zones maintained
on this server. These are used for reverse
mappings. The reverse mappings are updated automatically by FusionLayer
NameSurfer to keep them consistent with the corresponding forward
mappings, so you don't normally need to edit them by hand.
Creates a new zone to be maintained using FusionLayer NameSurfer.
Displays a node page where you
are asked to fill in the mandatory SOA and
NS records for the zone.
Otherwise the zone will be empty. You can then use "Add Host"
and related operations on the zone page
to create new names in the zone.
Statistics summary shows all relevant
statistic information about this DNS system. More detailed statistics can be
found from user and zone
statistics.
Creates a new zone to be maintained using FusionLayer NameSurfer by
importing the zone data from a text file
in /etc/hosts or RFC1035 master file format.
Creates a new zone to be maintained using FusionLayer NameSurfer by copying it
from another name server using a
zone transfer. This operation is
particularly useful when migrating an existing zone from another name
server to FusionLayer NameSurfer.
Creates new zones to be maintained using FusionLayer Namesurfer by transfering them
from existing name server
using AXFR.
The function transfer both forward and reverse DNS zones including
classless reverse zones and IPv6 reverse ip6.arpa.
This function allows you to use NameSurfer for handling zones mastered on another name server.
It works by using periodic zone transfers from the specified master server(s) to keep the data up to date in NameSurfer.
To add a secondary zone you must first give it a name and select a view as if you were adding a normal primary zone.
Additionally, at least one master server IP and port must be specified. If the zone being added has multiple master
servers, you can also list them all so that if one fails NameSurfer will be able to refresh the zone from another.
Option "Attempt DynDNS updates to this server" enables the management of the zone via NameSurfer. When the
option is enabled, modifications are sent to master server using DynDNS. After the secondary zone has been added
to NameSurfer, it will remain empty until NameSurfer is able to fetch data to it from one of the specified masters.
The secondary status of the zone will be shown in the status block on zone list page, along with a warning or error
marker if refreshing the zone from master server(s) hasn't been successful recently.
A link to the Views page,
where you can define and modify DNS views configuration.
DNS views allow the creation of multiple versions of one zone
which are shown differently to different DNS clients and secondary DNS
servers.
The transaction keys are in use in FusionLayer
NameSurfer since version 5.0, coexisting with the shared secret that resides in the
$NS/db/secrets file. Anyone who gains knowledge of the keys can
make changes to the DNS data, even remotely by TCP or UDP. The keys can be
configured to have only limited rights to DNS.
The zone list can be filtered using tags. Both the attribute as well as the value needs to be specified in order to be able to filter.
A user's tag-based restrictions apply to the zone list. The tag filter's names and values are truncated in the dropdown texts to 30 characters in order to keep the user interface readable. The full attribute or value text can be read by hovering the mouse over a select option. More information can be found on the page on tagging.