Free dns software for linux

Avahi is a framework for Multicast DNS Service Discovery on Linux.
It allows programs to publish and discover services and hosts running on a local network with no specific configuration.
For example, you can plug into a network and instantly find printers to print to, files to look at, and people to talk to.
Main features:
- Licensed under LGPL
- IPv4 and IPv6 support
- DBUS interface
- Drops all priviliges and runs as user "avahi"
- Embeddable mDNS stack (i.e. mDNS stack available as library)
- Support for loading static service definitions from XML fragments
- Interface to GLIBC NSS using [WWW]nss-mdns
- Ability to reflect mDNS traffic between multiple subnets
- Ability to configure a unicast DNS server automatically from server data published on the LAN

Webmin is a web-based interface for system administration for Unix.

Using any browser that supports tables and forms, you can setup user accounts, internet services, DNS, file sharing and so on.

GOsa is a PHP-based administration tool for role based managing of accounts and systems in LDAP databases.
Standard configurations can manage generic, posix/shadow, postfix/cyrus/sieve, pureftpd, fax and samba2/3 accounts in LDAP.
GOsa has plugins for DNS (BIND), DHCP (ISC dhcpd), and system/terminal management. The look and feel can be easily adapted to users needs.
Enhancements:
- This version fixes problems with automatic reverse zones in the DNS plugin, improves IE6/7 support, updates the available translations and fixes a couple of bugs in the FAI management dialog.
- Additionally, support for changing passwords without entering a fully blown GOsa has been added.

Linbox Directory Server (LDS), along with the Linbox Management Console (LMC), is a powerful system that allows developers, system administrators, and other software vendors to manage users, groups, and their associated policies in an LDAP server.
Linbox Directory Server is highly ergonomic interface design makes it very easy to use, and delegation of administration enables medium size organization to adopt LDS.
Enhancements:
- New features and improvements include DNS/DHCP management and a Norwegian translation.
- The new DNS/DHCP module allows you to manage DNS zones and DHCP subnets for a typical LAN environment.

Zero Calorie DNS is a domain name server for which the binary weighs in at 26K, that has no dependencies other than the minimal FreeBSD 6.0 installation.

The server responds to "name server" (NS), "start of authority" (SOA), "address record" (A), "reverse address" (PTR), and "mail exchanger" (MX) requests. The server is fairly fast because the feature set has been trimmed down to the bare minimum.

A few things are hard-coded so that a two minute setup is easy to accomplish. The hard-coding means that it may not be for everyone, however.

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

PowerDNS daemon Nameserver is a advanced, modern and high performance authoritative-only nameserver.
It is written from scratch and conforms to all relevant DNS standards documents. Furthermore, PowerDNS interfaces with almost any database.
The PowerDNS Nameserver utilizes, a flexible backend architecture can access DNS information from any data source. This includes file formats, Bind zone files, relational databases or LDAP directories.
If you have specific needs for your DNS infrastructure then you can use the Backend Developers Kit to write the glue between PowerDNS and your data or logic.
There is one master database that is replicated to two slave databases. The slave databases are read-only and are updated immediately when the master database changes.
For sites that do not yet have an existing database infrastructure we recommend the MySQL database. MySQL is very easy to setup and handles replication well.
If your nameservers are located on different physical networks then you immediately take advantage of the distributed nature of DNS. Questions will be load balanced on your array of servers. If a server is down then one of the other servers is queried.
PowerDNS is by default configured to serve all information directly from a database, which results in unmatched maintainability of your DNS information.
PowerDNS has developed a complete suite of technologies surrounding Internet Naming and email. Internet Naming is at the core of all online activities and is involved in each and every transaction on the net. Email remains the killer application of the Internet.
Enhancements:
- This release fixes many issues, unifies the PowerDNS Recursor and Authoritative DNS infrastructure (reducing code size by 2,000 lines), significantly improves the "BIND" compatibility mode (making real life zone loading up to 30 times faster than the original BIND), addresses many corner cases, reworks the TCP backend for improved stability, and makes 64 bit packages available.

mbridge provides a multicast DNS services bridge.

mbridge provides a bridge between LANs for multicast-announced services. As an example, you can use it to share iTunes libraries outside of your LAN with your peers.

It works by querying for and listening to announcements for instances of the desired service using the multicast DNS (mDNS) service discovery protocol.

Upon discovery of a new instance, it announces itself as the provider for that service on all the other LANs.

It then acts as a proxy between the clients and the real server.

How It Works

mbridge queries for and listens to announcements for instances of the desired service using the multicast DNS (mDNS) service discovery protocol.

Upon discovery of a new instance, mbridge announces itself as the provider for that service on all the other LANs. It then acts as a proxy between the clients and the real server.