Free posadis zone editor software for linux

Posadis is a powerful Domain Name Server for various platforms. It is supporting both authoritative DNS and caching functionality, which is available for different operating systems, including Mac OS X, Windows, and many Unix variants such as Linux and FreeBSD.
Main features:
- Caching and forwarding
- Primary DNS
- Secondary DNS
- Monitoring of zone files
- DNS Notify support
- DNS Update support (new in 0.70)
- Command-line tools
Enhancements:
- Removed "mc", "mc2" debugging messages
- Fixed "error: posadisrc:55: posadisrc:55: foo"-type messages
- Fix for "Line should not begin with whitespace" parser error
- Fix for Win32 service taking too long to stop
- Fixed bug where zone transfers would leave the TCP connection open
- Do not use Posadis thread system in signal handlers (could theoretically be harmful)
- Fix an occasion where Posadis could potentially flood itself with queries when resolving (depending on the underlying thread system)
- Added support for dumping the cache to file
- Added support for loading NXDOMAIN/NODATA information, and cached (as opposed to static) data from initial cache files
- Added option cache_to_file to load from file on startup and save to file on exit
- Default plugin dir works again now
- Fixed /really/ insignifficant error in serial number arithmetic code
- Fixed memory leak in dynamic zone lookup (not currently used)

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.

ZoneMaker is a script for making BIND zone files. ZoneMaker uses files similar to ini files to simplify updating several zone files simultaneously.
The script is fully capable of producing both normal and reverse zones as well as being able to produce HINFO, TXT and LOC records.
Currently there is no IPv6 support, although it is planned for a future release. Some knowledge about how zone files work is required to use this script effectively.
Main features:
- Supports both normal and reverse zones
- Supports a special global zone for using BIND9 views
- Supports a wide range of Record types
Installation:
After untarring the archive, youll want to first edit config.py. This file defines where the other files will be located. If you plan on running the script out of the tarball directory you should only need to modify OutputLocation.
Otherwise, change the options to suit.
The next step is to modify zones.conf and hosts.conf to suit your own needs a full list of options for each file can be found below
The format for hosts.conf and zones.conf is as follows
[section]
option1: value
option2: value
option3: value
In the above example, section would be the zone or host name. Options are not case sensitive, their values, however, are.

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.

SYNOPSIS

use Math::FresnelZone;
use Math::FresnelZone qw(fresnel fresnelMi fresnelKm);

The arguments are:

0 - distance in kilometers or miles (default is 1),
1 - frequency in GHz (defualt 2.4),
2 - set to true to specify that the distance you are inputting is in miles and that the results should be in in feet (default is 0 - IE kilometers/meters)
fresnel()

my $fresnel_zone_radius_in_meters = fresnel(); # fresnel zone radius in meters for 1 kilometer at 2.4 GHz

my $fzr_in_meters = fresnel(5); # fresnel zone radius in meters for 5 kilometers at 2.4 GHz

my $fzr_in_meters = fresnel(5,4.8); # fresnel zone radius in meters for 5 kilometers at 4.8 GHz

my $fzr_in_feet = fresnel(3,9.6,1); # fresnel zone in feet for 3 miles at 9.6 GHz

If you are inputting Kilometers the result is in meters (these 3 calls have identical results):

fresnel($Km,$GHz);
fresnelKm($Km,$GHz); # see documentaion below for info about fresnelKm()
fresnel($Km,$GHz,0);

If you are inputting Miles (by specifying a true value as the 3rd argument) the result is in feet (these 2 calls have identical results)

fresnel($Mi,$GHz,1);
fresnelMi($Mi,$GHz); # see documentaion below for info about fresnelMi()

fresnelKm()

You can use this to make it easier to avoid ambiguity if are working in kilometers/meters. It takes the first two arguments only: distance in kilometers and frequency in GigaHertz

my $fzr_in_meters = fresnelKm($Km,$GHz);

fresnelMi()

You can use this to make it easier to avoid ambiguity if are working in miles/feet. It takes the first two arguments only: distance in miles and frequency in GigaHertz

my $fzr_in_feet = fresnelMi($Mi,$GHz);

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.

The Public IP ZoneCD is whats known as a LiveCD. It does not install to your hard drive. It runs right from your CD-ROM. The ZoneCD is a re-master of Morphix CD which in turn is a modified version of KNOPPIX CD.
The ZoneCD is a bootable CD with a collection of GNU/Linux software pre-configured to create a WiFi gateway. ZoneCD is a mini operating system with automatic hardware detection, and support for many graphics cards, sound cards and other peripherals.
The gateway includes support for WiFi end-user authentication and web content filtering. Public IP ZoneCD is distributed under the GNU General Public License .
The ZoneCD is Linux, but you dont have to know anything about Linux to use the ZoneCD. You just need to know how to place a CD in a CD-ROM, and turn-on a computer? How cool is that!? All the benefits of Linux (stability, configurability, security, and a few other * itys) without having to know anything about Linux! We have Knoppix to thank for that.
Knoppix provides much of the auto configuration software used during bootup. Morphix provides the lightweight modular platform for me to add the components and software required to create an automatic WiFi gateway.
The ideal of Open Source is what makes the building and distribution the ZoneCD possible. The sharing of code so that the next developer can pickup and take the software in a new direction is what makes open source work. Its what makes the ZoneCD work.
The ZoneCD works by adding a piece of hardware between your AP (wireless access point or router) and your network or Internet connection. The piece of hardware used for the ZoneCD can be any PC with a minumum of 128MB RAM, two etherent cards, a floppy drive, and a CD-ROM (see system requirements). Once the initial setup and configuration is complete, the system can be run headless. Headless meaning there is no need for keeping a keyboard, mouse, or monitor hooked-up. The CD will boot completely unattended after setup is complete.
The ZoneCD has two very important services running that enable the system to operate as a self-contained wifi gateway. NoCat, and Dansgaurdian.
The features that are available to you depend on the mode in which you configure your ZoneCD to operate. The ZoneCD can operate in two modes, Open or Closed. Many of the Closed mode features are actually features that are available on the Control server in Zone Control. These features are available when the ZoneCD is operated in Closed mode and are not necessarily on the ZoneCD.
Main features:
Open Mode
- Homepage Redirection
- Customize ZoneCD splash page
- Content Filtering (block porn, downloads, etc.)
- Customize Firewall rules
Closed Mode
- User authentication/registration
- Homepage redirection
- Bandwidth shaping
- Daily time limits
- Daily download limits
- Zone open and close times
- Block by mac address
- Configure end-user network permissions(Classes)
- Customize firewall rules for each Class
- Content Filtering (block porn, downloads, etc.)
- Daily Log Mailer program
- Block traffic to *wired* network
- Customize ZoneCD login pages
- Branded "Terms of Use" template or use your own
- Usage statistics
- Multilingual login pages (Dutch,French,German,Spanish,English)
- End-User reporting