> >>Good question which TTL it uses in such case. From what it looks inthe > >>source it ignores the TTL of the CNAME record and uses the TTL of the A > >>record. Obviously it should use the least of the two... Please file a bug > >>report on this. > On Fri, 23 Sep 2005, Matus UHLAR - fantomas wrote: > >I don't think so. Is should use TTL as received, but reasonable maximum and > >minimum values can be used. On 23.09 23:08, Henrik Nordstrom wrote: > The key question here is what is "TTL as received" in > > www.example.com ttl=60 IN CNAME server1.example.com > server1.example.com ttl=360000 IN A 172.16.4.54 > > when the DNS query is www.example.com A. > > Squids DNS cache is quite simplistic and does not cache the CNAME > relations, only the A responses of the lookup. As a result today Squid > uses the ttl of the A record which is not entirely correct as this ttl is > for server1.example.com not the queried www.example.com. To conform with > normal DNS caching it should use the least of the two I think. Aha. This explains much. > But I won't touch this without a bug report where to keep a diary of the > change and preleminary patches. I filled up http://www.squid-cache.org/bugs/show_bug.cgi?id=1404 and I hope the description is clear enough -- Matus UHLAR - fantomas, uhlar@xxxxxxxxxxx ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Fucking windows! Bring Bill Gates! (Southpark the movie)
