NameSurfer Suite
REMSEC records (Automatic remote secondary update)
FusionLayer
HELP
  Table of contents
   Exit help

NameSurfer 7.6.4.1


When a zone is created added from a DNS master file or added by a zone transfer into NameSurfer, or when a zone is removed from NameSurfer, the secondaries for the zone need to be reconfigured. The BIND secondary running on the same machine as NameSurfer will be reconfigured automatically. The remote BIND secondaries, that is secondaries running on other machines, can also be set up for automatic reconfiguration. For details on how to do this, read the document doc/bindconf-install.html.

Remote Secondary name server (REMSEC) records are used to the define the remote secondaries that are set up to be configured automatically. This record should contain the full domain name for the remote secondary. Usually, these will be the same secondaries that are defined in the Authoritative Name Servers (NS) records. Note that you will not have to add the full domain name of the machine running NameSurfer to the Remote Secondary name servers.

The support for REMSEC records is a NameSurfer extension. REMSEC records are not part of the DNS standards. Like HTXT and HTML records, they cannot be retrieved by outsiders using DNS queries or zone transfers.