This page allows you to define server-specific default values for remote servers. These values will override the global defaults set in NameSurfer's configuration files.

Managed BIND/NSD/Secure64

The default master IP address and port settings affect the settings made for a zone when the remote server is selected as a secondary for it. Instead of using the system wide defaults, the IP address of the NameSurfer server and NameSurfer's internal primary port, the master settings of any zone added to the secondary will get these values as its master server setting. Only the addition of new secondary settings is affected, already defined secondaries will remain in their current values regardless of this setting.

Managed Unbound / Secure64 cache servers

Since Unbound and Secure64 cache servers do not operate as authoritative DNS servers, using them as remote secondaries for zones hosted in NameSurfer is somewhat different from other server types. Instead of creating a locally hosted zone data on these servers, setting one of these servers as remote secondary will create a stub zone entry there with NameSurfer defined as master, so all non-cached data will be queried from NameSurfer master by those servers, and there is no local copy of the whole zone data.
So, enabling the automatic addition of servers of these types as remote secondary on new zones triggers addition of a stub-zone entry on these servers.

FusionLayer DHCP Server

In order to integrate FusionLayer DHCP Server into FusionLayer NameSurfer you will have to enable and generate an API key in FusionLayer DHCP Server GUI, then transfer the key into Enter "Namesurfer's integration key" from FusionLayer DHCP Server here input field. The key is generated on the FusionLayer DHCP Server under System / Services / API Settings / NameSurfer Integration key by clicking "Generate" and "Save changes" buttons. Please also note that in order for the integration to work, system clocks on both FusionLayer DHCP Server and FusionLayer NameSurfer must be syncronized (5 minute gap is acceptable). You will get a clock skew error if your server clocks are not in sync. If your FusionLayer DHCP is configured to operate in IPv6 mode, be sure to set the correct operating mode for NameSurfer as well.

Microsoft DHCP Server

In order to integrate Microsoft DHCP Server into FusionLayer NameSurfer you must first add a Microsoft DHCP server to NameSurfer. After adding the server you will have to have an account available with DHCP Administrative rights, i.e. the account MUST belong to "DHCP Administrators" security group in the same domain that the managed DHCP server is. After providing the domain authentication information, NameSurfer will use it to communicate with Microsoft DHCP.

Remote server backup functionality for Secure64 cache server

Configuration data from Secure64 cache servers can be backed up into the NameSurfer server and the backups can be browsed via the NameSurfer GUI. The backup functionality is controlled by two options: a checkbox to enable the backup functionality, and a selector for determining the frequencey of backups - either daily, weekly or monthly. When the backup functionality is enabled, the timed background process responsible for statistics and backups initiates the first backup call, and then will repeat that operation whenever the specified time (1, 7 or 30 days) since the last backup has elapsed.