Free dns cache software for linux

Mod-Cache is a cache(reverse-proxy) accelerator plugin for lighttpd, which works like Squid with similar configuration. However mod_cache is faster and more effective than Squid because of powerful Lighttpd.
Mod-Cache has following advantages over Squid:
- Simpler. Mod-Cache just sets proper flags between lighttpd request handling stages. Request is handled by mod_staticfile or mod_compress or other modules.
- More Robust. Mod-Cache uses disk file instead of memory as cache. Without use of memory, mod_cache is far away from memory leaks and memory exhaustion.
- Faster. Lighttpd uses Sendfile syscall to service disk file. Sendfile syscall, which writes file to network interface directly, has the same effecience as Writev syscall which writes memory buffers to network interface.
- More Powerful. Mod-Cache can works with other lighttpd plugins(except mod_deflate). For examples, you can use mod_compress to compress cached files on-fly; or you can use mod_access/mod_trigger_b4_dl to do anti-hot-link; or you can use mod_flv_streaming to do native flv file streaming.
Enhancements:
- lighttpd 1.5 was upgraded to r1811.
- The status page for mod_status was added.
- cache.ignore-hostname was added.
- A bug for checking the cachehd file was fixed.

SafeCache is an extension which segments the cache on the basis of the document origin, defending against web-privacy attacks.

Segments the cache on the basis of the originating document, defending against web privacy attacks that remote sites can use to determine your browser history at other sites.

For example, a b.com image appearing on an a.com page would have a separate cache entry from the same image appearing on a b.com page, so a.com cannot use timing techniques to determine if you have visited b.com before.

Checks cookie settings (allow, originating site only, deny) to determine your desired privacy level (segmented cache, cache originating site only, or never cache).

OSCache is a high performance J2EE caching solution that can cache portions of JSP pages, entire HTTP responses (including dynamically generated images), and arbitrary Java objects.
OpenSymphony Cache can provide your J2EE application with huge performance gains and graceful error tolerance (e.g., in the event of a DB failure, cached content is served).
Fast in-memory caching
OSCache allows you to execute dynamic content periodically (eg every 30 minutes) rather than every request and store the result in memory. Each further request is served directly from the memory cache, resulting in dramatic speed increases.
The cache is keyed programmatically. This means you can calculate a cache key that works for your situation. For example an ecommerce site might use product ID as keys, or content site might use an article date and article ID combination.
The cache is stored in standard scopes that any JSP programmer is familiar with (application or session). The session scope allows you to have different cached content per user. This is one unlike any other caching system weve ever seen.
Persistent on-disk caching
OSCache can also write the cache to disk. This provides caching across server restarts, and caching of datasets that do not fit into memory. Caching can be configured to use memory or file caching, or a combination of both.
If you want to persist the cache to somewhere other than disk, you can plug in a custom PersistenceListener. This allows you to persist the cache to anywhere (for example to a database via JDBC or to LDAP via JNDI).
When using both disk caching and memory caching. It is possible to limit the cache size to avoid using too much memory but let disk cache unlimited, resulting in browser style complementary disk cache. When cached objects are removed from memory, they are still on disk. If the item is needed again and it is not expired the cache file will be used. This also gives fault tolerance if the server crashes.
Persistence can also be switched to overflow mode using the property oscache.persistence.overflow.only. This changes the default behavior (of persisting every cache entry when there is a listener) to only persist when the memory cache capacity has been reached.
Excellent Performance
Written with performance in mind.
Mulitple cache requests can be handled concurrently.
Only one requesting thread needs to update an expired cache entry even if multiple threads are requesting it simultaneously. Other threads can be configured to either receive the recently-expired object, or block until the cached object is updated. Similarly, when a new entry is being added to the cache, other threads requesting that entry will block until it is ready rather than run off and race to build the same object. In a high load environment this can provide enormous performance benefits.
Automatically takes advantage of JRE 1.4 or higher if available.
Clustering support
OSCache can easily be configured to cluster across multiple boxes. This provides both scalability and failover support without any changes required in your caching code.
Flexible Caching System
OSCache allows you to cache portions of JSP pages, arbitrary Java objects, and even entire servlet responses.
Cache capacity can be set allowing you to limit the number of cached objects.
Multiple caching algorithms are supported such as LRU (Least Recently Used), FIFO (First In First Out), or unlimited. It is also possible to plug in your own custom algorithm.
You are given a huge amount of control over the way cached objects expire. Objects can be cached indefinitely, expired once they reach a certain age, or expired based on a cron expression. Programmatic flushing is also possible, and if that is still not enough pluggable RefreshPolicies allow custom refresh strategies.
Cached objects can be grouped together however you like, allowing for powerful management of cached data. This is an extremely useful feature that is far more powerful than what other caching solutions typically offer (such as the flushing of cache keys that match a particular pattern).
Fully event driven! OSCache fires events for various happenings under the hood such as cache entry events (adding, updating, flushing and removing) and cache accesses (hit, stale hit and miss). It is easy to add your own event handlers.
Multiple caches can be created, each with their own unique configuration.
Simple JSP Tag Library
The tag library to perform and control the caching is very simple. See the Tag Reference for more information.
Caching Filter
A Servlet 2.3 Filter allows for caching of entire pages and generated binary files (like dynamically created images or PDF files).
Comprehensive API
For the ultimate control, OSCache can be used through its straightforward API. You can instantiate, configure and control multiple caches programmatically. It would be possible for example to create one small in-memory cache that held currency conversion rates and was updated daily at 2am, while another cache could be purely disk based and used for holding dynamically created images.
Exception Handling
OSCache provides a way for your site to gracefully tolerate errors. This is not error prevention, rather if an error occurs it should not stop your site from functioning. For example if your database goes down, normally your product descriptions will not be browsable. Using OSCache you can cache those descriptions so you can still browse them.
Cache Flushing
Flushing of caches can be controlled via JSP Tags, so these functions can easily be built into your administration interface.
There is programmatic control over what caches are flushed (eg all caches or just a particular scope).
Cached objects can be expired in a number of ways. Objects can be told to expire once they reach a certain age, or, through the use of cron expressions, on particular dates and/or times (eg it is trivial to make an object expire every weekday at 3am). If this is not enough, you can expire objects programmatically as required, or plug in your own custom RefreshPolicy class that can dynamically decide when an object should be flushed.
Entire groups of objects can be easily flushed from the cache. For example suppose you were caching product data as well as entire pages of your website. When a product was updated, you could flush not just the product object but also all the pages that contain information about that product. No more waiting for the cached objects to expire before the updated content shows up on your site!
Portable caching
Pure Java, this means it is platform independent.
OSCache is compliant with Servlet 2.3 and JSP 1.2 standards, which means it should work in the latest generation of servlet containers and application servers.
i18n Aware
The caching is i18n aware and supports all encodings.
Solid Reputation
Thousands of downloads, hundreds of users on the mailing list.
Comprehensive JUnit test suite that covers every aspect of OSCache, including a web stress test and various concurrent cache access scenarios. To back this up, the kind folks at Cortex have supplied us with a Clover license to provide detailed code coverage analysis of our unit tests.
We have solid issue tracking using JIRA to keep track of any feature requests, bug reports and development progress. JIRA is provided courtesy of Atlassian.
Enhancements:
- CRON expressions to expire content at specific dates and/or times.
- Pluggable EntryRefreshPolicy.
- Reduced memory consumption.
- Faster disk persistence.
- DiskPersistenceListener deadlocks are avoided if a process has no rights to delete the cache file.
- There is a new JSP tag _addgroups_, and an interface to get a list of the cache event listeners.
- The commons collection dependency has been removed.
- Java 1.3 support has been dropped.

CPAN::Cache is a Perl module abstract locally-cached logical subset of a CPAN mirror.

There have been any number of scripts and modules written that contain as part of their functionality some form of locally stored partial mirror of the CPAN dataset.

CPAN::Cache does the same thing, except that in addition it has the feature that the downloading and storage of CPAN data is all that it does, so it should not introduce any additional dependencies or bloat, and should be much easier to reuse that existing modules, which generally are more task-specific.

The intent is that this module will be usable by everything that is in the business of pulling modules from CPAN, storing them locally, and doing something with them.

In this way, it really does little other than mirror data from a remote URI, except that CPAN::Cache also provides some additional intelligence about which files are and are not static (will never change) which arent, and is typed specifically as a mirror of CPAN, instead of any other sort of mirror.

By building this module as a seperate distribution, it is hoped we can improve seperation of concerns in the CPAN-related modules and ensure cleaner, smaller, and more robust tools that interact with the CPAN in the most correct ways.

Smart Cache Loader is most configurable web batch downloader in world! If you have a very specific needs to grab some portions of web site -- this is right tool for you!
Operation
This program is command line driven. Forget slow GUI and other nice things. If you want GUI downloader, there are other programs. Main power of this program is configuration file. And yes this program has a very nice integration with Smart Cache proxy server.
Enhancements:
- Major bugfix release, now with HTML entity decoding.

pdnsd, written by Thomas Moestl, is a proxy DNS server with permanent caching (the cache contents are written to hard disk on exit) that is designed to cope with unreachable or down DNS servers (for example in dial-in networking).
pdnsd solves a frequently occurring problem with dial-up internet connections when the file /etc/resolv.conf changes after wwwoffled (a www proxy server) has been started up. (If youre interested in WWWOFFLE I also have patches available for it here.)
pdnsd allows you to configure one address as the DNS server for all your internet software. This can be localhost, but I personally use a separate machine that Ive configured as a gateway to the internet for my home LAN.
pdnsd project can then be configured to contact your ISPs DNS servers when you make a dial-up connection.
Enhancements:
- This release introduces a new query method: "udp_tcp".
- With this method, a UDP query is tried first and, if the UDP answer is truncated, the query is repeated using TCP.
- There is a new configuration option "use_nss", which can be turned off to prevent lengthy timeouts and stalls in certain situations.
- A bug has been fixed that previously could cause pdnsd to crash when started in debug mode.

DNS Domain Expiration Check is a utility for checking DNS domain expiration dates.

domain-check queries WHOIS data in realtime, and can be integrated with cron to provide e-mail notifications prior to a domain expiring.

The first example will print the expiration date and registrar for daemons.net:

$ domain-check.sh -d daemons.net

Domain Registrar Status Expires Days Left
----------------------------------- ----------------- -------- ----------- ---------
daemons.net INTERCOSMOS MEDIA Valid 13-feb-2006 64


The second example prints the expiration date and registrar for the domains listed in the file "domains":

$ domain-check.sh -f domains

Domain Registrar Status Expires Days Left
----------------------------------- ----------------- -------- ----------- ---------
sun.com NETWORK SOLUTIONS Valid 20-mar-2010 1560
google.com EMARKMONITOR INC. Valid 14-sep-2011 2103
daemons.net INTERCOSMOS MEDIA Valid 13-feb-2006 64
spotch.com GANDI Valid 03-dec-2006 357


The third example will e-mail the address admin@daemons.net with the domains that will expire in 60-days or less:

$ domain-check -a -f domains -q -x 60 -e admin@daemons.net