Looking at this, I'm inclined to say that libunbound is the better of the two options in spite of it being somewhat more difficult to consume DNS records than it would be with c-ares. In my estimation a (seemingly?) more-active community and the inclusion of a cache are more important. DNSSEC isn't a huge deal, at least not for me at this time, but is a nice bonus as well.
- Brad On Thu, Feb 12, 2015 at 10:01 AM, Joshua Colp <[email protected]> wrote: > Greetings all, > > I've extended the sections of my wiki page for c-ares[1] and libunbound[2] > to include further information about documentation, general usage > experience, and other aspects. Personally I lean towards libunbound because > it was straight forward to experiment with, supports DNSSEC, and has a > cache. > > Cheers, > > [1] > https://wiki.asterisk.org/wiki/display/~jcolp/DNS+Support+in+Asterisk#DNSSupportinAsterisk-c-ares > [2] > https://wiki.asterisk.org/wiki/display/~jcolp/DNS+Support+in+Asterisk#DNSSupportinAsterisk-libunbound > > > -- > Joshua Colp > Digium, Inc. | Senior Software Developer > 445 Jan Davis Drive NW - Huntsville, AL 35806 - US > Check us out at: www.digium.com & www.asterisk.org > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > asterisk-dev mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-dev -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
