Projects

BIND (Berkeley Internet Name Domain)

BIND (Berkeley Internet Name Domain) is an implementation of the Domain Name System (DNS) protocols and provides an openly redistributable reference implementation of the major components of the Domain Name System, including a Domain Name System server, a Domain Name System resolver library and ... [More] tools for verifying the proper operation of the DNS server. [Less]

Webmin

Webmin is a web-based interface for system administration for Unix. Using any modern web browser, you can setup user accounts, Apache, DNS, file sharing and much more. Webmin removes the need to manually edit Unix configuration files like /etc/passwd, and lets you manage a system from the console or ... [More] remotely. Webmin respects comments and configuration file order, is easy to install, includes dozens of translations, and runs on most Operating Systems. [Less]

djbdns

Small, secure dns cache and resolver written by Daniel J. Bernstein, the author of qmail. djbdns is extremely fast, very secure and easy to configure (think 'opposite of bind zone files').

PowerDNS

The PowerDNS server daemon is a versatile nameserver which supports a large number of backends. These backends can either be plain zonefiles or be more dynamic in nature. Additionally, through use of clever programming and caching techniques, PowerDNS offers very high domain resolution performance. ... [More] Prime examples of backends include relational databases, but also (geographical) loadbalancing and failover algorithms. The PowerDNS recursor daemon which is also part of the PowerDNS compilation is a dedicated high performance recursive (aka caching-only) Nameserver that already powers some larger broadband ISPs and as of late learned to embed Lua Scripts making it possible to manipulate DNS Answers from within those Scripts. [Less]

PowerDNS on Rails

PowerDNS is a reliable alternative to BIND and sports a flexible, feature rich design and support for various backends, including MySQL and PostgreSQL. This simplifies the management of thousands of zones, and provides added redundancy (by way of database replication) and opens the doors for web ... [More] frontends that ease this even more. PowerDNS on Rails is built based on our experience of managing thousands of DNS records through various (often crude) techniques, that included building zone files from databases via cron, and implementing PowerDNS for its database backends. PowerDNS on Rails is currently tightly integrated into one of South Africa's premier hosting & email platforms and works tirelessly everyday. [Less]

luasofia

LuaSofia is a Lua binding of Sofia-Sip library. Sofia-SIP is an open-source SIP User-Agent library, compliant with the IETF RFC3261 specification.

Strangle

Strangle is BIND for Python: a Python library for parsing DNS messages using libbind. Strangle allows you to see DNS messages in two ways: Direct access to the libbind parsing functions (C-style); and a Python object with various meaningful attributes (OO-style)

nschaind

nschaindnschaind is a tool that detects if a certain DNS resolver is vulnerable to cache poisoning according to VU#800113 (the Dan Kaminsky bug). This report covers weaknesses in BIND 9, BIND 8 and MS Windows DNS Server. This tool tests only the BIND weaknesses, which are described in VU#252735 and ... [More] VU#927905 (discovered by Amit Klein). The value of nschaind over other tools, is that nschaind does not require one to have direct access to the resolver being tested. The resolver must be tricked though into querying the tool, which can be accomplished in many ways. BackgroundIt comes down to this: bind versions up to 9.4.1 use a fixed source port for queries. This source port is determined at startup. Furthermore, they employ a bad PRNG for query IDs. This leads to predictability of the next query ID. One can exploit these two vulnerabilities together to send a resolver false DNS information, since all of the packet can be constructed and sent before a real server could: cache poisoning. In order to be vulnerable, a server would have a) the same source port for multiple requests and b)have predictable query IDs. To detect this, I followed the path Amit Klein described in his path: CNAME chaining. The tool acts as a DNS server. When a resolver sends a request for an A or MX record, it answers with a CNAME record within the domain, triggering another query from the resolver. And then, it does that again and again, up to 10 times. In these 10 times, the tool can determine if the source port was the same all the time, and if any of the IDs was predictable. Only when a query ID is even can the tool predict a range of 10 possible next query IDs (again, Amit Klein's approach). StatusAs of release 0.3, nschaind detects vulnerable BIND 8 and BIND 9 servers. UsageIn order to use nschaind to test a resolver, one should first startup the nschaind daemon. Then, the resolver in question should be triggered to perform a request to the nschaind server. An easy way to do so is to create a subdomain for which the nschaind server becomes the NS. Known issuesBIND 8 doesn't like to receive too many chained CNAME responses. In some cases, when prediction cannot be done after sending 8 responses, the resolver will stop querying and no results will be found. This is a rare condition which can be solved by trying again. This tool is further discussed at drainbamage.nl and in the README file included with release. [Less]

Acra DNS

Ancyradns fork BIND management software. It is specifically written for managing BIND configuration. It has a web GUI in PHP and a perl back end responsible for creating and managing zone files.

grig

grigУтилита предоставляющая интерфейс для управления файлами конфигурации сервера имен bind9.