[Unbound-users] AD flag inconsistency in "Wildcard Expansion" and "Wildcard No Data Error" query
W.C.A. Wijngaards
wouter at NLnetLabs.nl
Mon Jul 11 09:08:51 UTC 2011
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Jia Li,
On 07/08/2011 03:38 AM, Jia Li wrote:
>
>
> On 07/07/2011 17:28, W.C.A Wijngaards wrote:
>
>>/ /Could it be that you are using a version before 1.4.9, there is a fix
>>/ /listed: Fix no ADflag for NXDOMAIN in NSEC3 optout. And wildcard in
>>/ /optout, in unbound 1.4.9.
>
> I'm using version 1.4.11, besides, if unbound 1.4.7 being used, it
> would return ADflag in wildcard expasion case. I also noticed this fix,
> so got confused when encountered the inconsistency. I think maybe some
> cases are missed in the ADflag fix.
Yes you are completely correct. There was a missing if statement in
this exact case: wildcard expansion nodata under optout range. The fix
is submitted to our svn source.
Thank you for the report.
Best regards,
Wouter
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJOGr2dAAoJEJ9vHC1+BF+NffYQAIENtQQqablfqoFuT/uSoW9U
MNRF9Yk4uee/o2CNwkJlMPgYBp4WHVcKW3zVHp8kn4/KxN8z+4qmmqgHvu8JJfGO
bulhO8ETh0+be9hnEeGVY+ImD5NIithyhSTPFYslW3/gY+omkWiL1VaKMJmjE9z6
WMd+WNhpDZQ18QUefkHwcu9k/A77GkDkWxXgjynZCNJkNQpb4GdZanKuwYNmyRNN
3jc4t74bacMTCazhXcNVHWj0wXbctzl29mOuSFWo07NpS/uqrHHFKPRpn5lMQE7P
hz79f/1p1H2eybPslrYG/SRiwbqvxAcdwU9cIRS5ff2Kmd9Be/1qk9UZdG1nlo+1
tfd0AEHMPKeazjn5Jeq7OyV/gCjFL+Ta4qzo2HpNIxXWpa9hXTG6bIQElnKHdi4k
DRV69K2lJPAMjNW72sW0/0hwHtTzyru1oinAUt9LB0eP6eKpiUyEagrktAePIXXa
DFe4PMilban3+U/tukiGFVEvI+acYcOYwye9Oxs683xrdHHu3AeWjaP3AZ41XWN0
+8K++pL7OHaq0+sbCqNHHOeu9CaTJWOX5lGgPJi+Jiupa4D2peO/WTsSjxVqhQJz
uQ9W5hydxZmo0q7UvmHey+4CTxxhDeYJ3f+AhBDxMnvicZ79PpuiWkKlUVECw4PI
yj70K9L+kcqtm4JSRbeM
=ga+Y
-----END PGP SIGNATURE-----
More information about the Unbound-users
mailing list