Forgot to add, that I send only single one query to resolver: $ host w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.w.pl 127.0.0.1
Resolver properly returned response with A record, but host utility timeouts for some reason (it probably sends MX query subsequntyl). From valgrind report it looks that problem is in domain name / label compression code. By they way, in past there was very similar problem was CVE-2002-2097, which also was a bug in compression code in maradns. -- Witold Baryluk JID: witold.baryluk // jabster.pl
signature.asc
Description: Digital signature
