WAWAS is a full PHP application server. The main server core listens to any IP/port and passes data to any mounted protocol on the listener. Implemented protocols are HTTP1.1/1.0, Comet, Telnet, DNS, mail, and FTP. Each protocol runs modules that build response data based on the requests. Memory object persistence allows data and caches to be shared across protocols or time. All configuration uses XML. It can be launched as a daemon, with or without forked workers, and is nearly as fast as Apache in preliminary tests.
NicTool is a DNS management suite with support for various DNS servers (djbdns, BIND, PowerDNS), SQL data storage, DNS entry parsing (RFC 1034 & 1035 compliance), tiered and delegated permissions so you can safely grant access to clients and admins, giving them only the permissions they need. Humans interact via the Web interface, and an API is used for scripting mass updates, DNS templates, provisioning, and more. All changes are logged to easily track change history and see who changed what, and when.
PDNSOps, is a Web-based script which aids in administering domains and records for the PowerDNS SQL name server software. It is targeted mainly toward individual domain owners, but should be robust enough to be used in a larger capacity by an ISP or other big host. For those who may not know, PowerDNS is a domain name server application, much like BIND, but offering alternative backends for the storage of domain information.
NSC is a set of utilities for easy administration of DNS servers. You write very simple configuration files and NSC automatically generates zone files, reverse zone files, and configuration for the BIND. Among other things, it also supports classless reverse delegations and IPv6 addressing. NSC is written in POSIX shell and GNU M4, and it should run on all systems where these two languages are available. Generation of DNS daemon config files is currently limited to BIND 8 or 9, but it's very easy to add your own config file generators for other daemons.
mDNS Responder with Unicast runs on a server anywhere in a network and responds to mDNS queries across the network by performing a unicast DNS lookup and returning the result. Many networks use a .local top-level domain for their intranet. This has proven to be quite problematic as operating systems such as OS X have begun handling .local domains differently (in particular, prioritizing multicast DNS over conventional unicast DNS). Ideally, you'd have no problems moving away from a .local domain name, or simply not using one in the first place. That's not always possible, though. So with this tool, a lookup for "host.local" will be resolved via your existing unicast DNS servers, even if "host" does not have its own mDNS responder. Of course, the tool isn't limited to just .local domains, and can realistically work on any network where mDNS is in use.