shibari

What is it ?

shibari is a collection of DNS tools for Unix systems, as an alternative to BIND, Unbound, djbdns or other similar suites of programs.

It is an ongoing project; at the moment, only a DNS server is provided (one program to serve over TCP, another to serve over UDP). Currently, it relies on the s6-dns library, but it aims to integrate it over time, and eventually completely replace s6-dns (which is a badly named software collection, because despite being written by the same author and with the same mindset, it is not part of the s6 project).

Why "shibari"?

There's a de facto tradition that DNS software should have a name related to binding. shibari is the most pleasant of them.

Installation

Requirements

A POSIX-compliant system with a standard C development environment
GNU make, version 3.81 or later
skalibs version 2.14.1.0 or later. It's a build-time requirement. It's also a run-time requirement if you link against the shared version of the skalibs library.
s6 version 2.12.0.3 or later. It's a build-time requirement. It's also a run-time requirement if you link against the shared version of the s6 library. That library is used for the access control and client location features in shibari-server-udp.
(for now) s6-dns version 2.3.7.1 or later. It's a build-time requirement. It's also a run-time requirement if you link against the shared version of the s6-dns library.

Licensing

shibari is free software. It is available under the ISC license.

Download

The current released version of shibari is 0.0.1.0.
You can checkout a copy of the shibari git repository:
```
 git clone git://git.skarnet.org/shibari 
```
There's also a GitHub mirror of the shibari git repository.

Build and installation

See the enclosed INSTALL file for build and installation details.

Upgrade notes

This page lists the differences to be aware of between the previous versions of shibari and the current one.

Reference

Commands

All these commands exit 111 if they encounter a temporary error or hardware error, and 100 if they encounter a permanent error - such as a misuse. Short-lived commands exit 0 on success. Other exit codes are documented in the relevant page.