home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.protocols.tcp-ip.domains:722 comp.protocols.tcp-ip:5299
- Newsgroups: comp.protocols.tcp-ip.domains,comp.protocols.tcp-ip
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!Mongo-Jr.Empirical.COM!karl
- From: karl@empirical.com (Karl Auerbach)
- Subject: Re: Domain Name Service Deficiencies
- Message-ID: <karl.34.722564031@empirical.com>
- Keywords: DNS resolvers resolv.conf
- Sender: usenet@news.arc.nasa.gov
- Organization: Empirical Tools and Technologies
- References: <4285@bcstec.ca.boeing.com>
- Date: Tue, 24 Nov 1992 00:13:51 GMT
- Lines: 15
-
- In article <4285@bcstec.ca.boeing.com> tld5032@bcstec.ca.boeing.com (Terry Davis) writes:
- >From: tld5032@bcstec.ca.boeing.com (Terry Davis)
- >Subject: Domain Name Service Deficiencies
-
- > 11) In addition to DNS, the resolver routines "gethostbyname"
- > and "gethostbyaddr" need some extensive enhancements for life in
- > the network environment. Some form of short lived caching needs
- > to be provided, probably a most recent "10" lookups would be more
- > than adequate for anything except servers.
-
- My PC-based DNS resolver implements a local name cache which it uses
- before ever hitting the disk or the network. Seems to work OK for my PC
- applications.
-
- --karl--
-