[reSIProcate] Assertion failure/crash in ARES

Gabriel Hege gabriel-mailinglists at gmx.de
Wed Nov 26 10:11:03 CST 2008


Hi!

I came across a problem in ares with misbehaving(?) nameservers. I have 
been using a nameserver (130.149.2.12), which does not give a "No such 
name" response, when queried for nonexistent domain names but a list of 
some additional records.
In debug builds this causes an assertion failure in file dnsstub.cxx 
line 223: assert (!soa.empty());
This naturally leads to an error with release builds in line 225: 
RRCache::instance()->cacheTTL(key, rrType, status, soa[0]);

I am not all that familiar with DNS, that I could say whether the DNS 
server is actually misbehaving or not, but I can supply Wireshark logs 
if that helps.
Anyhow I think it should gracefully fail - misbehaving servers or not.

best regards,
  gabriel



More information about the resiprocate-devel mailing list