An analysis of wide-area name server traffic: a study of the Internet Domain Name System
SIGCOMM '92 Conference proceedings on Communications architectures & protocols
Selecting locking primitives for parallel programming
Communications of the ACM
Netscape Enterprise Server
SWEB: Towards a Scalable World Wide Web Server on Multicomputers
IPPS '96 Proceedings of the 10th International Parallel Processing Symposium
Redirection Algorithms for Load Sharing in Distributed Web-server Systems
ICDCS '99 Proceedings of the 19th IEEE International Conference on Distributed Computing Systems
lbnamed: A Load Balancing Name Server in Perl
LISA '95 Proceedings of the 9th USENIX conference on System administration
System design issues for internet middleware services: deductions from a large client trace
USITS'97 Proceedings of the USENIX Symposium on Internet Technologies and Systems on USENIX Symposium on Internet Technologies and Systems
The content and access dynamics of a busy Web site: findings and implications
Proceedings of the conference on Applications, Technologies, Architectures, and Protocols for Computer Communication
| Hi-index | 0.00 |
When a web server wants to learn the domain name of one of its clients, it must perform a lookup in the Domain Name System's "reverse domain", inaddr.arpa. These lookups can take time and may have an adverse impact on the web server's response to its clients. Rapid DNS is an intermediate client/server system that operates between a web server and a DNS server. It provides caching of the results and, more importantly, limits web server lookups to the data contained in the cache. This provides a significant improvement in response time for situations in which knowledge of the hostname is not critical to the web server's operation. The Rapid DNS system was implemented for use in the web farm that serves the collection of Cable News Network (CNN) sites. Its design is presented, along with measurements of its performance in the CNN environment.