Free what is a dns error software for linux

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

The Posadis Zone Editor is a graphical tool to edit DNS (Domain Name System) zones using DNS update.

Because it uses zone transfers, you can simply edit the DNS zone, and have only the changes transferred to the DNS server.

mod_ssl_error is a X.509 certificate validation error trapping (SSL).

Valid errors are:

unable to get issuer certificate
unable to get CRL
unable to decrypt certificate signature
unable to decrypt CRL signature
unable to decode issuer public key
certificate signature failure
CRL signature failure
certificate not yet valid
certificate has expired
CRL not yet valid
CRL has expired
error in certificate "not before" field
error in certificate "not after" field
error in CRL "last update" field
error in CRL "next update" field
out of memory
depth zero self signed certificate
self signed certificate in chain
unable to get issuer certificate locally
unable to verify leaf signature
certificate chain too long
certificate revoked
invalid certification authority
path length exceeded
invalid purpose
certificate not trusted
certificate rejected
subject issuer mismatch
"akid" skid mismatch
"akid" issuer serial mismatch
"keyusage" different from "certsign"
unable to get CRL issuer
unhandled critical extension
"keyusage" not for CRL signing
unhandled critical CRL extension

libgpg-error package contains common error codes and error handling functions used by GnuPG, Libgcrypt, GPGME and more packages.

Installation:

Please read the file INSTALL!

Here is a quick summary:

1) Check that you have unmodified sources. You can find instructions how to verify the sources below. Dont skip this - it is an important step!

2) Unpack the archive. With GNU tar you can do it this way:

"tar xzvf libgpg-error-x.y.tar.gz"

3) "cd libgpg-error-x.y"

4) "./configure"

5) "make"

6) "make install"

tinydyndns is a simple but powerful dynamic DNS solution that uses djbdns. tinydyndns cooperates with the djbdns package to publish dynamic IP addresses authenticated through POP connections.

On successfully authenticated POP connections, the tinydyndns-update program manipulates tinydns constant database "data.cdb" directly without rebuilding it; this makes the dynamic DNS solution use very few system resources.

Using a POP service for authentication saves the work for installing special client software, since POP clients are available for every common network-aware operating system. To provide the DNS and POP service, tinydyndns cooperates with djbdns, qmail, and cvm.

DNS Flood Detector was developed to detect abusive usage levels on high traffic nameservers and to enable quick response in halting (among other things) the use of ones nameserver to facilitate spam.
DNS Flood Detector uses libpcap (in non-promiscuous mode) to monitor incoming dns queries to a nameserver. The tool may be run in one of two modes, either daemon mode or "bindsnap" mode. In daemon mode, DNS Flood Detector will alarm via syslog.
In bindsnap mode, the user is able to get near-real-time stats on usage to aid in more detailed troubleshooting.
Usage: ./dns_flood_detector [OPTION]
-i ifname specify interface to listen on (default lets pcap pick)
-t n alarm when more than n queries per second are observed
(default 40)
-a n wait for n seconds before alarming again on same source
(default 90)
-w n calculate statistics every n seconds
(default 10)
-x n use n buckets
(default 50)
-m n mark overall query rate every n seconds
(default disabled)
-A addr filter for specific address
-M mask netmask for filter (in conjunction with -A)
-Q monitor any addresses (default is to filter only for
primary addresses on chosen interface)
-b run in foreground in "bindsnap" mode
-d run in background in "daemon" mode
-D dump dns packets (implies -b)
-v detailed information (use twice for more detail)
-h usage info
Sample Output:
dopacki:~$ sudo ./dns_flood_detector -v -v -b -t10
[15:14:56] source [192.168.1.45] - 0 qps tcp : 24 qps udp [8 qps A] [16 qps PTR]
[15:14:56] source [10.0.24.2] - 0 qps tcp : 15 qps udp [15 qps A]
[15:15:06] source [192.168.1.45] - 0 qps tcp : 24 qps udp [8 qps A] [16 qps PTR]
[15:15:06] source [10.0.24.2] - 0 qps tcp : 15 qps udp [14 qps A]
[15:15:16] source [192.168.1.45] - 0 qps tcp : 23 qps udp [7 qps A] [15 qps PTR]
Enhancements:
- Address filtering options are now available, as are fractional query rates for better precision.
- This update also fixes several crashes and segfaults that affected overall reliability.

Domain Details 2.4 will empower your browser with nifty features. It is actually a Firefox addon that allows you to view the current site's server software and headers, IP address, location flag, and have quick links to Whois and other domain information.