All tools and demos from this area are designed to work with DNS Manager 4.0.1 or newer.
4PSA Social Networks Community-powered support for 4PSA 4PSA on Facebook 4PSA on Twitter 4PSA Blog 4PSA Youtube
Skip to end of metadata
Go to start of metadata
This document is an overview of the 4PSA DNS Manager 4 architecture.

DNS RFC Compliance

DNS Manager complies to the RFC listed below.

Aspect

RFC

Details

A recordRFC 1035 
AAAA recordRFC 3596 
CNAME recordRFC 1035 
MX recordRFC 1035 
NAPTR recordRFC 3403 
NS recordRFC 1035 
PTR recordRFC 1035 
SRV recordRFC 2782 
TXT recordRFC 1035 
SOA recordRFC 1912 - for default values for SOA records 
SERIALRFC 1912Supports both RFC 1912 and timestamp SOA Serial number formats.
Classless delegationRFC 2317Classless routing allows allocation of subnets on non-octet boundaries that is less than 256 addresses from a Class C address.
E.164RFC 3761DNS zones for storage of E.164 numbers
IPv6 zonesRFC 4291Reverse DNS lookups for IPv6 addresses.
Mask delimitersRFC 4183Both / and - are supported as mask delimiters.

Zone Dump

The zone dump file format that is used by DNS Manager remote update protocol has been improved with:

Dump File Examples

Master Zones Examples

Default Zone Type is Master

If the zone type is missing, it is assumed to be a master zone definition.

Slave Zones Example

Slave zones may be included in dump as follows.

Classless Delegation

The rules mentioned above also apply to reverse DNS zones. You can see below full DNS zones with /24 /28 and /32 subnet mask.


$ORIGIN, @ and Blank Substitution

The "@" character is accepted when defining zones. It is substituted with:

  • The last $ORIGIN directive encountered in the file, or

  • If no $ORIGIN directive is present - it is generated automatically

Blank Substitution - with the last valid name (or label) or $ORIGIN if there are no previous names (labels).

Mask Delimiter

Both "-" and "/" character are accepted when defining reverse zones. The zones are different!

SOA Records

If the SOA records are not found in the zone definition, they are inherited from the client preferences, if the client has SOA records defined. If the client has no SOA records defined, the system wide SOA settings defined by the administrator are used.

E164.ARPA Reverse Zone

Check the below example of E.164 reverse zone that contains all the supported record types, NS and NAPTR:

IP6.ARPA Reverse Zone

Check the below example of IP6.ARPA reverse zone that contains both supported record types, NS and PTR:

Primary NS

The primary NS record is marked with 1 in the dump file. If missing the NS order is random.

Dump Export Utilities

Command Line Utilities

The export command line utilities support the new dump file format. These utilities help you set the 4PSA DNS Manager server to act as slave DNS for other servers.

The dump export utility should be copied on the primary server. To find out more details about how to configure Primary/Secondary Server Setup with 4PSA DNS Manager read this KB article.

Dump Scripts

New dump scripts are provided for major control panels on the market. The new dump scripts can export both master and slaves zones. Export settings are set as variables in the script or in the configuration file.

Use this command to find the DNSMANAGER_ROOT_D path:

Below you can find the list of export scripts available:

Zones management software

Folder

4PSA DNS Manager Script

Bind genericDNSMANAGER_ROOT_D/remote/bindbind_export.sh
DNS ManagerDNSMANAGER_ROOT_D/remote/dnsmanagerdnsmanager_export.sh
Plesk LinuxDNSMANAGER_ROOT_D/remote/pleskplesk_export.sh
plesk_export.pl
Plesk WindowsDNSMANAGER_ROOT_D/remote/plesk_winplesk_win_export.exe
PowerDNSDNSMANAGER_ROOT_D/remote/powerdnspowerdns_export.sh
Helm Control Panel for WindowsDNSMANAGER_ROOT_D/remote/helmhelm_complete.exe
helm_export.exe
helm_zones.exe
InterWorx Hosting Control PanelDNSMANAGER_ROOT_D/remote/iworxiworx_complete.php
iworx_zones.php
EnsimDNSMANAGER_ROOT_D/remote/ensimensim_complete.sh
ensim_zones.sh

Services

Please find below a list of all services on a DNS Manager 4 server.

Web Interface Service
  • Name - dnsmanager
  • Short description - The service is responsible for running 4PSA DNS Manager web interface
  • Init script - Usually located in /etc/init.d/dnsmanager
Zone Management Service
  • Name - zonemngd
  • Short description - The service synchronizes the bind configuration file with updates (received using any means)
  • Init script - Usually located in /etc/init.d/zonemngd
Remote Import Service
  • Name - updateurld
  • Short description - The service synchronizes DNS Manager local database with remote updates
  • Init script - Usually located in /etc/init.d/updateurld
BIND Service
  • Name - bind
  • Short description - BIND (Berkeley Internet Name Domain) is an implementation of the DNS (Domain Name System) protocols; BIND includes a DNS server (named), which resolves host names to IP addresses, a resolver library (routines for applications to use when interfacing with DNS), and tools to verify that the DNS server is operating properly.
  • Init script - Usually located in /etc/init.d/named
Round Robin Service
  • Name - rrmonitd
  • Short description - Automates the DNS Round Robin disqualification and qualification when a resource associated with a resource record becomes unavailable/available again.
  • Init script - Usually located in /etc/init.d/rrmonitd

Interface Access and Disk Location

4PSA DNS Manager comes with a dedicated web management interface, accessible in the browser at:

To login to the interface for the first time, you must supply the following login credentials:

The skin directory can be found in:

DNSMANAGER_ROOT_D/admin/htdocs/skins

The language pack directory can be found in:

DNSMANAGER_ROOT_D/admin/htdocs/language

Icon

All important paths are defined in /etc/dnsmanager/dnsmanager.conf

  • No labels