XACK DNS

XACK Inc. has been providing RADIUS servers, DHCP servers, and DNS servers to various carriers since providing RADIUS servers for mobile carriers in 2003. It has been highly evaluated by customers and has been used for a long time.

XACK DNS has the following features:

1.Highly reliable, purely Japanese commercial DNS server All source code is developed in-house, and is free from vulnerability issues originating from open source (such as BIND) code. This reduces the operational burden of applying emergency patches for open source.

2.Improved system stability by ensuring diversity

• By ensuring system diversity through mixed operation with other products such as BIND (for example, changing part of the DNS cache server to XACK DNS, changing the slave side of the authoritative name server to XACK DNS, etc.), it is possible to provide continuous service and avoid operational risks as a countermeasure against zero-day attacks due to unknown vulnerabilities.
• Smooth migration is also possible without stopping the system.

3.Easy system migration and inheritance of operational know-how.

• A migration support tool from BIND is bundled with the product, making system migration a smooth reality.

• XACK DNS configuration files (dnsd.conf, master.conf, slave.conf, client.conf) can be automatically generated from BIND configuration file (named.conf).
• Zone files can be used as is.

4.Name resolution using our own in-memory DB

• A DNS-specific in-memory DB developed in-house to store zone information allows for dramatic performance improvements.
• Includes a DB tool that displays various statistics about zone information: Type statistics: Displays current statistics for each data type and resource type Process statistics: Displays process statistics for each interval time TTL statistics: Displays the current number of registered resource records for each TTL

5.Highly flexible customizability

• The program uses the dynamic shared object (DSO) method, and all source code is developed in-house, so it is possible to customize with great flexibility according to customer needs.
• Customization examples:

• DB integration of zone information (when zone information is managed with SQL)
• Implementation of external IF (SOAP, etc.) for integration with subscriber management systems
• External notification using various OSS (MIB compatible/SNMP compatible/syslog compatible)
• Response editing function for client control (responding with NXDomain as a response code to clients that do not support NotImp)
• Server status notification for the purpose of load balancing between cache servers