Free nameserver software for linux

Dnstracer determines where a given Domain Name Server (DNS) gets its information from, and follows the chain of DNS servers back to the servers which know the data.
Enhancements:
- Better handling of timeout (instead of a static value, start with five seconds and double it each retry)
- Warnings are printed if you receive a different RR type than the one you asked for (for example when you ask for an A record and receive a CNAME)
- Fixed problems when records received in the authority field are shorter than the domain the nameserver is authoritative for.
- When compiled without IPv6 support on an IPv6 capable machine the machine tried to query the IPv6 translated IPv5 address anyway.
- -C caches hosts which havent answered too.

beware project is a distributed global server load balancing system.

beware is a small DNS server that can have nameserver responsibility delegated to it and that can return a set of authoritative "IN A" records to a client.

Given a list of hosts for a certain domain name, it also tests for services specified and will only return IP addresses for currently reachable services.

mod_defensible project consists of an Apache module which blocks spammers.
mod_defensible is an Apache 2.x module intended to block spammers using DNSBL servers. It will look at the client IP, check it against one or more DNSBL servers, and return a 403 Forbidden page to the client.
Installation Instructions:
Just run ./configure. You can specify several useful options like:
--with-apxs=path_to_apxs
To specify the path to the apxs2 binary (/usr/bin/apxs2 is default).
--with-udns
To compile mod_defensible with udns support (better performance).
This options needs libudns.
Then, type make and make install as root.
Configuration example:
DnsblUse On
DnsblServers bsb.spamlookup.net bl.blbl.org opm.blitzed.org sbl-xbl.spamhaus.org
If compiled with udns support, you can use a special nameserver with:
DnsblNameserver 127.0.0.1
Enhancements:
- This release enhances some autoconf features and adds support for Limit and Location blocks.

web-nsupdate is a web-based dynamic DNS update utility.

The web-nsupdate package provides a simple, web-based facility for clients to send dynamic DNS updates. Clients are typically DHCP hosts, such as a Linux system acting as a gateway for residential broadband service.

The client sends a simple web request (such as with the wget(1) or lynx(1) commands) to the web-nsupdate service to register their host request.

This package has been tested on a server with the following Debian packages:

* bind9 (ver 9.2.4-1)
* apache2 (ver 2.0.54-5)
* php4 (ver 4.3.10-16)

BE ADVISED: Its a pain in the butt to configure BIND to do dynamic DNS. You are going to need to do that to make "web-nsupdate" work. These instructions describe that process, so follow carefully. I *strongly* urge you to review the dnssec-keygen(8) and nsupdate(8) man pages first, so you can get some idea of what we are trying to accomplish.

Installation Instructions:

1. Copy the "web-nsupdate" files to a location such as
"/usr/local/lib/web-nsupdate". It is OK to install somewhere else,
just adjust the following directions accordingly.

2. Generate a TSIG key that "web-nsupdate" will use to authenticate
itself to the DNS server.

SECURE THIS KEY! Do not leave readable copies around. This key can
be used to make changes to DNS records managed by "web-nsupdate".

Here are the steps to generate the key:

cd /usr/local/lib/web-nsupdate
/usr/sbin/dnssec-keygen -a HMAC-MD5 -b 512 -n HOST web-nsupdate
chmod 440 Kweb-nsupdate*
# Below, adjust "www-data" to the GID your web server runs under.
chgrp www-data Kweb-nsupdate*

3. Setup the "web-nsupdate" definitions file, starting with the provided
sample. This file needs to be secured, to protect the client passwords
from being revealed.

cd /usr/local/lib/web-nsupdate
cp nsupdate-defs.php.sample nsupdate-defs.php
chmod 640 nsupdate-defs.php
# Below, adjust "www-data" to the GID your web server runs under.
chgrp www-data nsupdate-defs.php
vi nsupdate-defs.php

4. Verify that "nsupdate.php" has the correct path to the "nsupdate-defs.php"
file.

vi nsupdate.php
# Check the require_once() statement near the top.

5. Symlink the update script into your web site.

# Below, adjust "/var/www/nsupdate.php" to a location in your web server.
ln -s /usr/local/lib/web-nsupdate/nsupdate.php /var/www/nsupdate.php

At this point, the "web-nsupdate" front-end is configured. Now to
configure the nameserver back-end.

6. Assuming you dont already have a place for nameserver keys, create
a new file called "named.keys" that contains the TSIG key that
"web-nsupdate" will use. The file will look something like:

key web-nsupdate {
algorithm HMAC-MD5;
secret "jzzoMR4ocgZGq5pQho2Pr5r9DDHT4lWK8QO09cpvVtpvHqaUdzktBs1DHCslpPR8PwXU3ni8zjST/5FxEwg44Q==";
};

Replace the "secret" value show above with the key in the
"Kweb-nsupdate.+157+nnnnn.private" file you generated in step 2.

7. Install the "named.keys" file to the directory where your "named.conf"
resides. This file needs to be secured, to protect your namesever
from unauthorized updates.

If your "named.conf" directory is "/etc/bind", do:

# Below, adjust /etc/bind to directory where named.conf lives.
mv named.keys /etc/bind/named.keys
chmod 400 /etc/bind/named.keys
# Below, adjust "bind:bind" to the UID:GID your nameserver runs under.
chown bind:bind /etc/bind/named.keys

8. Add a line to your "named.conf" that says:

include "named.keys";

9. Modify your "named.conf" to list each host that web-nsupdate will
be updating. If, for example, you want to allow dynamic updates
from hosts "host1.example.com" and "host2.example.com", then modify
the "example.com" stanza in "named.conf" and add two lines:

zone "example.com" {
type master;
.
.
.
# add the lines below, one per host in thie zone
update-policy {
grant web-nsupdate. name host1.example.com. A;
grant web-nsupdate. name host2.example.com. A;
};
};

10. Test the update capability. Point your web browser to the installed
"nsupdate.php" script. This should bring up a form for manual
entry. Submit your entry, and verify the update was successful.

NSD is a complete implementation of an authoritative DNS nameserver.
NSD is an authoritative only, high performance, simple and open source name server.
NSD is thoroughly tested, there is a regression tests report available on the home page.
NLnet Labs has a long term commitment for supporting NSD. There will be an advanced notice when our commitment ends. The latest NSD release will supported for at least two years after this notice.
Enhancements:
- AXFR/IXFR zone transfer supported.
- NSD requests but does not provide IXFR transfers.
- NSD keeps track of SOA timeouts for secondary zones.
- TSIG authentication supported.
- For queries, for notifies, for zone transfers.
- NOTIFY messages of zone updates, incoming and outgoing.
- DNAME type is supported, including CNAME synthesis.
- config file, nsd.conf(5), place to put TSIG keys, server settings, and lists of ip-addresses/ranges for AXFR/IXFR and NOTIFY.

Dirsave is graphical utility for intellectually generated senteces urls from you links (example: pic01,pic02 or pic1,pic2).

After generate with 3 clicks you execute program and wget download this files.

Its no hard type:

http://nameserver/folder/pic1.jpg
http://nameserver/folder/pic2.jpg

or

http://nameserver/folder/docum01.xml
http://nameserver/folder/docum02.xml

Its yesterday day!

Dirsave program automatically generate links (and choise 1,2,3 or 01,02,03 or 001,002,003 numeration)!

Its easy and quick!

PowerDNS Oracle Backend provides a backend which allows PowerDNS to use Oracle as its data store.

PowerDNS Oracle Backend is a backend driver for the PowerDNS nameserver which allows DNS data to be stored in an Oracle database. PowerDNS can load backend modules at runtime. This backend is fully configurable, and SQL statements can be specified in the configuration file.