Free dns zone 0.85 software for linux

DNS::ZoneParse is a Perl module to parse and manipulate DNS Zone Files.

SYNOPSIS

use DNS::ZoneParse;

my $zonefile = DNS::ZoneParse->new("/path/to/dns/zonefile.db", $origin);

# Get a reference to the MX records
my $mx = $zonefile->mx;

# Change the first mailserver on the list
$mx->[0] = { host => mail.localhost.com,
priority => 10,
name => @ };

# update the serial number
$zonefile->new_serial();

# write the new zone file to disk
open NEWZONE, ">/path/to/dns/zonefile.db" or die "error";
print NEWZONE $zonefile->output();
close NEWZONE;

INSTALLATION

perl Makefile.PL
make
make test
make install

The purpose of this project is to provide a simple, generic GUI database browsing frontend. The tool is a very simple aggregation of the Qt database classes.
The database abstraction is provided by the Qt database drivers. So far, the drivers for PostgreSQL and MySQL have been found to work well.
In principle, there is no reason why ODBC drivers for popular databases such as Oracle, DB2, Informix as well as Firebird and SAP/DB shouldnt work via the Qt ODBC3 abstraction layer.
However, some preliminary tests with these have not been promising. It may be that the only way to get some of these working is to create a native Qt database driver. This is something Ill be looking into much later.
At the moment, it is only possible to build the system on Unix and similar systems. Since Trolltech have released a version of Qt for OSX under the GPL and have announced their intention to do likewise for Win32, it should be possible to provide ports for both of these platforms. For the moment though, I just provide the source.
Main features:
- Tree browser for databases and tables
- Display of table descriptions
- Display of table contents in main window
- Execution of ad-hoc SQL queries in the query tab
- Command line history in the query tab
- Retrieval of database connection details from XML config file
- Retrieval of other configuration parameters from XML config file
- Prompting for connection password
- Addition of new connections via GUI to the running application and the config file
- Display database views with a separate icon
- Create a connection name independent of the database name
- A "Test" button when creating a new connection
- Dynamically generate a list of available drivers
- Configuration via autoconf
- Fixed bug with executing updates/inserts twice
- Refreshing of a DB connection
- Deleting of connections via the GUI
- Editting of connections via the GUI
- Check for the existence of ~/.qtsql
- Creation of skeleton config file
- Auto saving/restoring of history
- Loading of queries
- Saving of results
- Keyboard shortcuts

DNSDusty is my answer to the above problems that I saw in existing web-based DNS management tools.

All updates to DNS are done through the dynamic DNS interface, using signed updates. There is no external database. It simply does a zone transfer when it needs to get a listing of records.

It has worked well for me so far on my home DHCP/DNS server, which uses the ISC BIND and DHCP server. It has very basic functionality at this point. You can add records one at a time, and can delete them via checkboxes.

Installation:

DNSDusty comes set up to be installed according to the Debian packaging guidelines. The sources also come with an EPM listfile. If you have the EPM program installed (see http://www.easysw.com), then you should be able to package the software by running:

% epm -v -f native dnsdusty

Once you generate the package, install it with your OSs installation tool.

Youll then need to modify the config file, which is by default at etc/dnsdusty/dnsdusty.conf.

The config file should only be writable by root, and only readable by the user that your webserver runs as. Since it contains the key to allow updates to your webserver, make sure that you secure it well, unless you want the world to be able to update your server.

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

Zonestats create an RRD database with the values of CPU and memory (RSS) usage per Solaris 10 zone. Zonestats project requires only the RRDs Perl module.

ZoneAdmin is a Web interface for the powerDNS name server using the MySQL backend. It allows you to manage existing zones and add, remove, and alter new ones, supports on-the-fly input validation, and allows comments per zone and per record.
Furthermore, it keeps a detailed history of changes and allows you to temporary enable or disable zones without having to remove them completely. New zones can use templates that contain predefined records. The project is designed to be used with one of Apaches authentication methods.
Enhancements:
- This release fixes bugs related to inability to add record type AAAA, inability to add CNAME records, and validation failures.

Xtemp is a SuperKaramba theme that shows temperatures of 3 sensors in your motherboard.

This theme is configured for MSI k7n2 (Nforce2), if your motherboard is not Nforce2 edit the theme files and change the sensors.

**Remember**
**This theme needs lm_sensors installed and correctly configured.
**Install the fonts they are in Xtemp/fonts .

Wait 4 sec after open to full reload

The style is based in aSensors http://kde-look.org/content/show.php?content=15756
The background of thermometer is based in acpimon http://kde-look.org/content/show.php?content=9059