id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	uname	nginx_version
329	resolver: incorrect TTL used with A+CNAME response	Sergey Kandaurov		"By default, nginx caches responses using the TTL value of a response.

The resolver doesn't fully operate correctly on multiple entries
received together in one DNS response.
For example, when the received answer contains multiple records as follows:
upstream 60 CNAME cname1
cname1  86400 A 10.10.10.10

Here the CNAME resolution stage would be ""skipped"", and the resolver cache
will store for ""upstream"" a finally resolved address with TTL 86400.

References: http://mailman.nginx.org/pipermail/nginx-ru/2013-April/050744.html"	defect	closed	minor		nginx-core	1.3.x	fixed	resolver			n/a