
|
Frequently Asked Questions about Caching Name Server
What is Nominum Foundation Caching Name Server?
Nominum Foundation Caching Name Server is a caching only domain name server that has better performance than any other caching name server. Nominum Caching Name Server delivers superior throughput, as measured in name resolutions per second. In addition, Nominum Caching Name Server with Response Validation (RV) provides protection against potential attacks on a widespread network vulnerability in business applications running on UNIX systems. The vulnerability is described in a recent alert issued from the Computer Emergency Response Team (CERT).
Back to top
What are the suggested hardware configurations for Nominum Foundation Caching Name Server?
Nominum Foundation CNS runs on the following platforms:
Red Hat Linux, SuSE, and FreeBSD on Intel: CPU: Pentium IV 2.4GHz or faster processor RAM: 1GB Disk Space: 2GB
Sun Solaris 8 and 9 on SPARC: CPU: UltraSPARC III 1.2 GHz or faster processor RAM: 1GB Disk Space: 2GB
Back to top
Is Nominum Foundation Caching Name Server a version of BIND?
No, Nominum Foundation Caching Name Server is a totally new domain name server, written from a totally fresh code base. It is designed for optimum performance in an environment that supports a high volume of client queries.
Back to top
How do I purchase Nominum Foundation Caching Name Server?
For pricing information please contact Nominum Sales at sales@nominum.com.
Back to top
How is Nominum Foundation CNS with Response Validation (RV) a unique solution?
Nominum Foundation CNS with RV is a unique solution to the buffer overflow vulnerability because it does not require every application that uses the affected resolver libraries to be rebuilt with new "fixed" libraries. Because of the RV feature, Foundation CNS screens all DNS packets it sees to make sure they are not malformed or malicious. Thus, not only is the Nominum Foundation CNS server itself free from this vulnerability, but Foundation CNS can protect applications downstream from it from receiving bad packets.
Back to top
|
|
| Product Resources |
| White Papers |
|