| Reporter: |
|
Pete Zaitcev zaitcev |
| Created: |
|
Mon, 15 Sep 2008 14:32:00 |
| Updated: |
|
Tue, 16 Sep 2008 02:10:05 |
| Key: |
|
462394 |
| Versions: |
|
Not provided |
| Environment: |
|
x86_64 |
| Priority: |
|
3 |
| Status: |
|
Opened |
| Resolution: |
|
Not provided |
| Original Link: |
|
https://bugzilla.redhat.com/show_bug.cgi?id=462394 |
| Summary: |
|
nscd ignores configured caching time |
Description:
Description of problem:
The nscd only caches for a few minutes, although /etc/nscd.conf says
positive-time-to-live hosts 3600
Version-Release number of selected component (if applicable):
nscd-2.8.90-12.x86_64
How reproducible:
Steps to Reproduce:
1. run tcpdump -n in the background
2. run date(1) to timestamp
3. run "host ipv6.google.com"
4. check output of step 1, it has DNS requiest for AAAA ipv6.google.com
5. re-run steps 1-3, see that there is no DNS traffic -- this is good
6. wait 20 minutes
7. repeat steps 1-3
8. observe that there's DNS traffic again
Actual results:
Short lifetime of cache
Expected results:
Configured lifetime
Additional info:
Setting bug component to glibc because nscd has no its own component.
The replied TTL from Google is rather goofy, only 35s for AAAA:
ipv6.google.com. 6340 IN CNAME ipv6.l.google.com.
ipv6.l.google.com. 35 IN AAAA 2001:4860:0:2001::68
However, nscd caches for more than 35 seconds, so I think it obeys
wrong part of nscd.conf or something.
Created an attachment (id=316788) [details]
nscd.conf
Comments:
Reported Issue
