Search in this section
The application DNS REST BIND forms a bridge between AutoDNS and a BIND name server, allowing the zones in AutoDNS to be managed. The actions required for this in AutoDNS are passed to the BIND server with the help of DNS REST BIND. The REST protocol based on HTTP is used to do this. In order to ensure a secure connection, we suggest that you start the server in SSL mode. You can either integrate your own certificates or use the certificate already in place in the application.
The AutoDNS actions are processed in two steps:
- The order data is checked and saved in the relevant queue. The corresponding BIND zone data is also generated and saved.
- All open orders are carried out and the AutoDNS configuration file is rewritten. After this is done, the BIND server is restarted. This step is asynchronous, but the interval can be adjusted.
The application requires a Java Virtual Machine (JDK). It is also dependent on the javad-util package, included in delivery. Although there are no special hardware requirements, we nevertheless recommend an x86 system with at least 128 MB storage.
We use the OpenJDK Amazon Corretto-8 to develop our software, therefore we recommend the usage of Amazon Corretto-8. Amazon Corretto is a free, cross-platform and production-ready distribution of the Open Java Development Kit (OpenJDK). Corretto provides long-term support that includes performance enhancements and security fixes. It can be installed easily using the following commands:
First import the repository
rpm --import curl -L -o /etc/yum.repos.d/corretto.repo
Finally install the JDK:
yum install java-1.8.0-amazon-corretto-devel
Installation using package manager yum
DNS REST BIND was designed for use with systems based on RPM and is available as an RPM package. As soon as the InterNetX repositories are available, DNS REST BIND can be installed easily using the following command:
yum install dns-rest-bind.rpm
The package manager resolves the requirements and enables the installation of missing programs.
The server uses HTTP BASIC Auth to authorize the user. You can define the users and corresponding passwords in the file passwd in the configuration index.
The file uses the following format:
Rest-user cannot be changed and must follow the password – it defines the user group specified in the server.
The file log4j.xml is saved in the configuration index at installation.
The file defines the logging behavior. This is based on "Log4j-Logger". It writes the log data to
/var/log/javad/dns-rest-bind.info.log file. Logging is set so that a maximum of 1 GB hard drive space can be used, i.e. 10 files of 100 MB each.
If you would like to perform the logging via e.g. syslog, please refer to the "Log4j" configuration.
Configuration of the BIND connection
The following parameters are defined in the configuration folder under bind.properties:
|The path to the job spool directory.
|The path to the zone files directory, must be also defined within the bind conf.
|The path to the RNDC command.
|The path to the specific AutoDNS BIND definition file. The file will be generated by the application.
|Reload every minute in milli seconds, after the time of seconds the bind server is reloaded, using the RNDC command.
|The path to the
|The path to the
|The bind user group.Default:
|The path to the named-checkconf command.Default:
|The path to the name-checkzone command.Default:
|The AXFR timeout in seconds.Default:
|The local address to bind.Default:
Server start parameters
The server starting parameters are defined in the tables.
These can be modified under
/etc/sysconfig/javad/dns-rest-bind under the item PARAM.
|Server port that waits for requests.
|Is HTTPS used instead of HTTP? For SSL further parameters are required.
|Password for the SSL keystore. The password is stored AES encrypted.
|Password for the certificate. The password is stored AES encrypted.
|Path to the user file.
|IP Address the server should bind to.
|Path to the multiserver configuration.
|The user the server is started with.
|Defines JDK specific parameters like memory usage.
|Start parameter for the server. See: Configuration of the Server Start Parameters.
Default: see server parameters
|Starts the VM with JMX.
|The JMX port.
|Starts the VM in the remote debug mode.