Free dns zone software for linux

DNS::Zone contains a collection of Perl modules which provide an abstraction of name service zones as well as server specific adaptors for concrete file representations.

The modules origin is the ZoneMaster project which make heavy use of the module for comprehensive zone file management. Go to http://www.zonemaster.org for further information.

Installation:

You install DNS::Zone as you would install any perl module library, by running these command:

If you have CPAN.pm installed and are connected to the Internet

perl -MCPAN -e shell
> install DNS::Zone

or even

perl -MCPAN -e install DNS::Zone

otherwise

perl Makefile.PL
make
make test
make install

Net::DNS::ZoneFile is a Perl extension to convert a zone file to a collection of RRs.

SYNOPSIS

use Net::DNS::ZoneFile;

my $rrset = Net::DNS::ZoneFile->read($filename[, $root]);

print $_->string . "n" for @$rrset;

my $rrset = Net::DNS::ZoneFile->readfh($fh[, $root]);

# OR

my $rrset = Net::DNS::ZoneFile->parse($ref_to_myzonefiletext[, $root]);

This module parses a zone file and returns a reference to an array of Net::DNS::RR objects containing each of the RRs given in the zone in the case that the whole zone file was succesfully parsed. Otherwise, undef is returned.

The zone file can be specified as a filename, using the ->read() method, or as a file handle, using the ->readfh() method. If you already have a scalar with the contents of your zone file, the most efficient way to parse it is by passing a reference to it to the ->parse() method.
The optional $root parameter, tells the module where to anchor $INCLUDE statements found in the zone data. It defaults to the current directory.

In case of error, undef will be returned.

The primitives $ORIGIN and $GENERATE are understood automatically.

Note that the text passed to ->parse() by reference, is copied inside the function to avoid modifying the original text. If this is not an issue, you can use ->_parse() instead, which will happily spare the performance penalty AND modify the input text.

dnsutl package is a collection tools to make administering DNS easier. These include:
dns-rev
Take the forward DNS mapping and generate the reverse mapping. This is useful for producing a self-consistent DNS configuration.
dns-ethers
By using a bogus record type, you can keep the MAC address with the IP address, and generate the /etc/ethers file.
dns-hosts
Take the forward DNS mapping and generate the /etc/hosts file.
dns-bootp
Using the MAC and IP information, you can generate the /etc/bootptab file.
dns-ng
Take the forward DNS mapping and generate the /etc/netgroup file.
dns- bootparams
Using the MAC and IP information, you can generate the Sun /etc/bootparams file.
dns-boot- check
Check your named(8) configuration for self- consistency.
dns-hosts-import
Turn your /etc/hosts file into a DNS forward map, as a first step to configuring your DNS server.
dns-dhcp
Using the MAC and IP information, you can generate the /etc/dhcp.conf file.
All of these programs are both faster than shell scripts, and more robust when faced with all the peculiar semantics of DNS resource files. They even understand the $include directive.
dnsutl runs on almost any flavor of UNIX. The source distribution is self configuring using a GNU Autoconf generated configure script.
Enhancements:
- A bug has been fixed in the SRRF parser, so it more closely follows RFC 1035.
- A bug has been fixed in the name server (ns) record validation.

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

DIY Zoning is a repository containing the information about architecting, designing and implementing the Do It Yourself Temperature Zoning system, introductory course for those planning to install a ready-made temperature zoning system, and those who just want their home comfort.

Whats New in This Release:

This release introduces support for many logical devices per one physical 1-Wire device in general, and humidity sensor support in particular.

DAC2CORE protocol has changed, backward compatibility is broken. To upgrade your configuration, you have to add a literal T in front of 1-Wire temperature sensors, and add a literal S in front of 1-Wire switch devices.

MyDNS is a free DNS server for UNIX. It was implemented from scratch and is designed to serve records directly from an SQL database (currently either MySQL or PostgreSQL).
Its primary objectives are stability, security, interoperability, and speed, though not necessarily in that order.
MyDNS does not include recursive name service, nor a resolver library. It is primarily designed for organizations with many zones and/or resource records who desire the ability to perform real-time dynamic updates on their DNS data via MySQL.
MyDNS starts and is ready to answer questions immediately, no matter how much DNS data you have in the database. It is very fast and memory-efficient. It includes complete documentation, including a manual and a FAQ.
MyDNS supports a few frills, including round robin DNS, dynamic load balancing, and outgoing AXFR for non-MyDNS nameservers.
MyDNS is licensed under the GNU General Public License
Enhancements:
- Changed PostgreSQL connect error message code. It will still try the Unix domain socket (not sure why I did that) but if all fails, it outputs the first error message, which is much more likely to make sense.
- Implemented David Phillips AIX patch.
- Implemented Petter Larssons ALIAS patches for mydnscheck and mydnsexport.
- Made sure all copyright notices included 2004.
- Fixed "undefined constant" and other strict error message stuff in contrib/admin.php.
- Fixed reference to "rr" (table name) in contrib/admin.php -- replaced with $rr_table_name.
Thanks to Harald Paulsen for finding this.

DNS name parser is a Java utility library for parsing dns names, ip and hw addresses.

Synopsis

import su.netdb.parser.*;

Parser parser = new Parser();

Hashtable result = parser.parse(str);

System.out.println("string: "+result.get("string"));
System.out.println("hw: "+result.get("hw"));
System.out.println("name: "+result.get("name"));
System.out.println("domain: "+result.get("domain"));
System.out.println("ip_low: "+result.get("ip_low"));
System.out.println("ip_high: "+result.get("ip_high"));

"DNS name parser" is an utility library created to be used in a search application. Given a single input field its function is to differentiate between several types of possible input strings. Namely if it a dns name, IP address (exact, ip range or ip with wildcards) or hardware address. The result of the parsing is a Hashtable with possible keys "string", "hw", "name", "domain", "ip_low" and "ip_high".

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.