Carlos E. R. wrote:
On 2017-01-09 19:35, Per Jessen wrote:
Carlos E. R. wrote:
On 2017-01-09 16:02, Per Jessen wrote:
Carlos E. R. wrote:
Usual (trivial) setting: use dnsmasq to cache dns searches for one machine only.
Just thinking out loud - isn't that what nscd does too? Every call to the resolver tries nscd first.
Well, apparently dnsmasq is more effective. Caches more entries and longer. Often I disable nscd.
Okay - whoever does the caching should adhere to the TTL from DNS, but I guess dnsmasq could be "more efficient". I never had any reason to play with it.
I always used bind as cache server (the default configuration) because it speedied things when using a modem. Dnsmasq is far easier to use.
Yeah, bind is running here anyway, so that caches things too, nscd just takes a little load off it. If you have an upstream bind, they will also be caching.
Whether this still happens with a fast Internet connection, I don't know. It would be interesting to have a comparison, and include nscd in the mix.
A bit of an academic exercise, nscd is reached by local socket, anything that involves network traffic will be slower. Whatever the difference, it'll be a contrived situation with little or no bearing on reality. :-) -- Per Jessen, Zürich (-0.6°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org