On 16 May 2012 07:41, JD <jd1...@gmail.com> wrote: > I have nscd running. > /etc/resolv.conf starts out with > nameserver 127.0.0.1 > nameserver 192.168.1.254 > > > The 192.168.1.254 is the router, which has been a fast and reliable > resolver. > > So, to test nscd caching behavior, > I browse (using FF) over to any website. > After some time, the address is resolved and the page comes up. > I kill the tab of the page, and open a new tab and aim the browser > at same url. Browser again says: looking up whatever....com and takes > several seconds to resolve it. > > I thought that nscd is supposed to cache the translation from the > first lookup. > > Am I to believe that the browser is NOT using /etc/resolv.conf? > If not, what is it using? > Or could it be that nscd is useless in this respect?
nscd should cache host lookups if it is configured correctly. Run nscd -g to see caching statistics and see if they tally with your usage. If all of them are misses then you need to run nscd in debug mode with 'nscd -d' to see why the caching is not working. Make sure you increase the value of debug-level to get verbose messages. An easy test is to use 'getent hosts <hostname>' and 'getent ahosts <hostname>' and study the nscd logs to see if you get a cache miss everytime. -- Siddhesh Poyarekar http://siddhesh.in -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
