Ports Search

ldapdns is a lightweight, high performance DNS server which utilizes LDAP as its backend. It was originally based on djbdns, and strives to maintain the same goals of performance, security and simplicity.

From the website: ldap2dns is a program to create DNS (Domain Name Service) records directly from a LDAP directory. ldap2dns is designed to write ASCII data files used by tinydns from the djbdns package, but also may be used to write .db-files used by named as found in the BIND package.

Combined DHCP/DNS Server for Small LAN. Dynamic DHCP allocates/renew host addresses while Caching DNS Server first try resolving from DHCP allotted names then from Cache then only forwarding to External DNS Servers. Auto Config and auto Dynamic DNS update.

This port contains a subset of djbdns (net/djbdns) - a DNS client library released to the public domain by its author. The library was packaged by Gerrit Pape. The port contains both static and shared versions of the DNS client library.

dnscap is a network capture utility designed specifically for DNS traffic. It normally produces binary data in pcap(3) format, either on standard output or in successive dump files (based on the -w command line option.) This utility is similar to tcpdump(1), but has finer grained packet recognition tailored to DNS transactions and protocol options. dnscap is expected to be used for gathering continuous research or audit traces.

sheerdns is a master DNS server whose zone records are stored on a one-record-per-file bases. Because of this, sheerdns is likely the simplest DNS to configure, use, update, and operate. It's especially efficient for networks with frequent updates -- serving DHCP, for example. Updates to the zones are immediate, and do not require restarting sheerdns. SheerDNS is a good candidate for creating and RBL for mail, or web sites, as well as for providing DNS on embeded systems. Or anything else that requires a fast DNS, with very low overhead.

`dlint' is a Domain Name Server zone verification utility. `dlint' analyzes any DNS zone you specify, and reports any problems it finds by displaying errors and warnings. Then it descends recursively to examine all zones below the given one (this can be disabled with a command- line option). You can run dlint on your own domains, or on somebody else's, because it uses the standard DNS network protocol. Dlint is very useful since most nameservers do no more than syntax-check your database files. Dlint's messages are very informative and suggest ways to fix the problems, not just complain about them.

Totd is a small DNS proxy nameserver that supports IPv6 only hosts/networks that communicate with the IPv4 world using some translation mechanism. Examples of such translation mechanisms currently in use are: * IPv6/IPv4 Network Address and Packet Translation (NAT-PT) implemented e.g. by Cisco. * Application level translators as the faithd implemented by the KAME project (http://www.kame.net). See faithd(8) on *BSD/Kame.

Fastresolve is a package of programs to process web log files to get DNS and domain ownership information for log analysis. It sends out many queries in parallel, and caches results, for speed. Its DNS resolver is about 10 times as fast as logresolve.pl from the Apache 1.3.9 distribution, and about 50 times as fast as logresolve.c from that distribution. It is 5-20 times as fast as the adnslogres program that comes with the adns library, and about 3 times as fast as jdresolve, which is a Perl program that uses similar algorithms.

from nsping.8: Nsping uses DNS queries to monitor reachability and operation of name- servers, as well as the latency of DNS queries. It does this by sending random recursive DNS queries to the nameserver (avoiding the effects of DNS caching) and measuring the amount of time between the sending of the query and the receipt of the response packet.