<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><pre style="white-space: pre-wrap; background-color: rgb(255, 255, 255);" class="">On 01/07/2019 08:32 AM, Simon Kelley wrote:
><i class=""> I've worked through the patch, and been inspired to clean up a few
</i>><i class=""> long-standing nasty bits. This has the consequence that the mechanisms
</i>><i class=""> which were added to enable storage of DNSKEY and DS RRtypes during the
</i>><i class=""> the DNSSEC campaign are now much more general, and I've used them to
</i>><i class=""> implement SRV caching. The new code is therefore all mine, as are any
</i>><i class=""> bugs, but the net effect is the same as Jeremy's (I hope).
</i>><i class="">
</i>><i class="">
</i>><i class=""> I didn't implement a config switch to disable caching of SRV records,
</i>><i class=""> because I can't conceive of a situation where such would be necessary.
</i>><i class="">
</i>><i class="">
</i>><i class=""> Code is in the git repo now, and we're eating the new dog food here.
</i>><i class=""> Please test away.</i></pre><div class="">New to the list but just wanted to report my experience with the “new dog food”.</div></div><div class=""><br class=""></div><div class="">I use dnsmasq in Docker and have a script that will fully build my configuration from the official Ubuntu docker image and the dnsmasq git repository HEAD. Its been working well for almost a year now. I only once had to rollback a commit when it broke compilation and after some waiting, a new commit fixed the issue.</div><div class=""><br class=""></div><div class="">After updating to commit 5b99eae59d59a8e34a7e512059b98bbd803312f2 today, I’m finding that it dies with a "Segmentation fault (core dumped)" in about 30 minutes or less.</div><div class=""><br class=""></div><div class="">I compile it with CFLAGS='-Wall -W -O2 -DNO_IPV6 and launch it with /usr/local/sbin/dnsmasq -d --log-facility=/var/log/dnsmasq.log</div><div class=""><br class=""></div><div class="">If you have any advice on capturing more information about the segfault, let me know.</div><div class=""><br class=""></div><div class="">-Daniel</div></body></html>