Free multicast dns software for linux

Emcast project is a generic multicast toolkit.
Emcast is a multicast toolkit for distributed/peer-to- peer applications that require multicast communication.
It includes the program "emcast", a generic multicast utility (like netcat), and the library "libemcast", a generic multicast library.
Emcast supports IPv4 multicast (IM) and can easily support almost any end-host multicast (EM) protocol.
The EM protocols supported are Banana Tree Protocol (BTP) and Internet Relay Chat (IRC).
Enhancements:
- Copy from inet address, not string. Interesting that mcast was still working before in Linux.

libasyncns provides a C library for Linux/Unix for executing name service queries asynchronously. It is an asynchronous wrapper around getaddrinfo and getnameinfo from the libc.
In contrast to GNUs asynchronous name resolving API getaddrinfo_a(), libasyncns does not make use of UNIX signals for reporting completion of name queries. Instead, the API exports a standard UNIX file descriptor which may be integerated cleanly into custom main loops.
In contrast to asynchronous DNS resolving libraries like libdenise, skadns, adns, libasyncns is just an asynchronous wrapper around the libcs synchronous getaddrinfo() API,
which has the adva ntage of allowing name resolution using techniques like Multicast DNS, LDAP or NIS using standard libc NSS (Name Service Switch) modules.
libasyncns is compatible with IPv6 if the underlying libc is.
libasyncns is very tiny, consisting of just one header and one source file. It has no dependencies besides libc.
By default libasyncns spawns a number of worker threads (LWPs) to process name queries. Alternatively or when POSIX Threads are not supported, libasyncns can fork() off worker processes instead.
Installation:
As this package is made with the GNU autotools you should run ./configure inside the distribution directory for configuring the source tree. After that you should run make for compilation and make install (as root) for installation of libasyncns.
Enhancements:
- This version properly detects res_query() on Linux/AMD64 and supports older autoconf versions.

UDPcast project is a file transfer tool that can send data simultaneously to many destinations on a LAN. This can for instance be used to install entire classrooms of PCs at once.
The advantage of UDPcast over using other methods (nfs, ftp, whatever) is that UDPcast uses Ethernets multicast abilities: it wont take longer to install 15 machines than it would to install just 2.
UDPcast is released under the GPL 2.0 license.
UDPcast can be started from the included linuxrc boot disk for OS installations, or from the command line when using it for other purposes.
Enhancements:
- The kernel was upgraded to 2.6.21.3 and busybox was upgraded to 1.5.1.
- The code was adapted to Solaris 10 x86 by adding includes and configure checks.
- A patch was made to fix parallel make and make DESTDIR=/tmp/xxx install.
- gcc4 warnings were addressed.

KpassDNS will help you to define bookmarks in hosts file and speed up your connection while connecting these websites.

Also using KpassDNS, you can bypass DNS level censor. If you define website and IP with KpassDNS, DNS level censor cant stop you.

Blahz-DNS is PHP/MySQL based DNS (BIND 9/tinydns) administration with support for primary and secondary zones, user authentication, User and Admin account types (with read-only versions), and restricted access for user accounts to certain primary and secondary zones.
Enhancements:
Bugfixes:
- Search and replace now places updated zones into the updated table
Additions:
- Added import functionality. Will allow you to import zone files
- This is done by performing a dig @< dnsserver > < domain > AXFR and then parsing that output and inserting values into the DB.
- Added Search UI mode. Allows traditional listing mode and Search mode.
Changes:
- Swapped position of Write Zones and Restart server buttons since the old order didnt makes sense as you have to write the zones before restarting the server.

tinydyndns is a simple but powerful dynamic DNS solution that uses djbdns. tinydyndns cooperates with the djbdns package to publish dynamic IP addresses authenticated through POP connections.

On successfully authenticated POP connections, the tinydyndns-update program manipulates tinydns constant database "data.cdb" directly without rebuilding it; this makes the dynamic DNS solution use very few system resources.

Using a POP service for authentication saves the work for installing special client software, since POP clients are available for every common network-aware operating system. To provide the DNS and POP service, tinydyndns cooperates with djbdns, qmail, and cvm.

RIR to DNS converter is a tool to convert Regional Internet Registry data to a DNS country lookup zone. You can use it to build your own DNS zone for looking up country codes from IP addresses.

It uses data directly from RIPE, ARIN, APNIC, LACNIC, and AFRINIC. The data can be updated on a schedule of your choosing.

The input data comes from:

ftp://ftp.afrinic.net/pub/stats/afrinic/delegated-afrinic-latest
ftp://ftp.apnic.net/pub/stats/apnic/delegated-apnic-latest
ftp://ftp.arin.net/pub/stats/arin/delegated-arin-latest
ftp://ftp.ripe.net/pub/stats/ripencc/delegated-ripencc-latest
ftp://ftp.lacnic.net/pub/stats/lacnic/delegated-lacnic-latest

The input data format is described in:

http://www.apnic.net/db/rir-stats-format.html

The output is a BIND 9 zone file that can be used to look up country codes
in a similar fashion to in-addr.arpa. For example, to find out what country
203.30.47.58 is:

host 58.47.30.203.rir.example.com
58.47.30.203.rir.example.com has address 127.0.65.86

where 65 and 85 are ASCII for A and U, which means 203.30.47.58 is
in Australia (AU).

HOW TO USE IT

Just feed it the above delegated- -latest files into stdin and it will
spit out the zone file to stdout. The zone file will only have the IP addresses,
so you could $INCLUDE it into a zone file that contains NS records, SOA, $ORIGIN,
etc.

WHY USE IT

You dont need the resolution of MaxMinds GeoIP database, but you do want
something that is free and you want it kept up to date on a schedule that
you decide.

You could use this to block or tag email based on countries, block or redirect
visitors to your website based on end-user country, and so on. Be very
careful about blocking mail this way, though, as you may block legitimate
email. Instead of blocking outright, use it in a SpamAssassin rule to add
something to the spam level, based on where the email comes from.

HOW IT WORKS

The RIR files contain ranges of IP addresses, and indicate what CC each range is allocated to. At the simplest level, rir2dns just sorts the ranges then iterates
through the IPs in each range and generates a reverse-dns-style A record that
represents the country code.

HOW IT WORKS - IN DETAIL

Rather than iterate through each IP address, the program tries to skip through
entire classes at a time (256 IPs, 65536 IPs, etc). Rather than iterate
through each IP, the loop iterates through classes or IP ranges (whichever are
smaller at the loop control), using control-breaks to accummulate neighbouring
ranges where possible so that entire classes that are in the same country dont
generate huge numbers of records.

Firstly, IPs are considered to be 4-digit numbers, but in base-256. In other
words, each octet is dealt with as if it were a single base-256 digit. This
turns out to be convenient because optimisations of large chunks of IP space can be done by looking for places where least-significant base-256 digits are zero.

Next, IP ranges are broken down into the following sub-ranges:

Optional individual IP addresses (ie: 4 octets)
Optional A-class ranges (ie: 3 octets)
Optional B-class ranges (ie: 2 octets)
Optional C-class ranges (ie: 1 octet)
Optional B-class ranges (ie: 2 octets)
Optional A-class ranges (ie: 3 octets)
Optional individual IP addresses (ie: 4 octets)

Considering that there is a pattern here, Im sure theres an elegant way to
handle breaking this down into two loops (one reducing the octets and one
increasing the octets), but I cant be bothered, so Ill break it down into
seven loops. Kind of hard-coded, but at least its simple.

For ease of processing, the IP addresses are actually converted to 32-bit numbers, then back again. This simplifies mathematics and looping through ranges.

Thats pretty much it, really...

Note that currently there are about 80,000 RIR records between all five
registries. This takes about 35 seconds on a 2.4GHz P4 to process, and
generates a 26MB file with around 3/4 million lines (RRs). This causes BIND
to use about 100MB or so of memory, and on a slow machine will probably cause it to take too long to reply, while it searches the zone. That size zone can
take a minute or two to load, which is quite a while.

Basic algorithm:

Read & process RIR data:

Read RIR ranges
Sort RIR ranges by start IP address
Glue together contiguous ranges of the same country

For each range

Generate the IPs at the start of the range

Generate the A-classes at the start of the range

Generate the B-classes at the start of the range

Generate the C-classes in the middle of the range

Generate the B-classes at the end of the range

Generate the A-classes at the end of the range

Generate the IPs at the end of the range

ctDSM project is the distributed shared memory related modules of the Coral Tree Library Set.

This includes:

DSS (Distributed Shared memory System)
A library-based distributed shared memory system implemented using TCP as the underlying transport. KM (KeyMaster)
A shared resource management system obsolesced by NRM except for the fact that DSS is dependent on KM.

NCS (Network Chunk Sysytem), A library-based distributed shared memory system implemented using reliable IP Multicast as the underlying transport. NRM (Network Resource Manager), A network shared resource manager.