[Dnsmasq-discuss] Patch to cache SRV records - updated version (#3)

[Mufasa]

On 01/07/2019 08:32 AM, Simon Kelley wrote:
> I've worked through the patch, and been inspired to clean up a few
> long-standing nasty bits. This has the consequence that the mechanisms
> which were added to enable storage of DNSKEY and DS RRtypes during the
> the DNSSEC campaign are now much more general, and I've used them to
> implement SRV caching. The new code is therefore all mine, as are any
> bugs, but the net effect is the same as Jeremy's (I hope).
> 
> 
> I didn't implement a config switch to disable caching of SRV records,
> because I can't conceive of a situation where such would be necessary.
> 
> 
> Code is in the git repo now, and we're eating the new dog food here.
> Please test away.
New to the list but just wanted to report my experience with the “new dog food”.

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.

After updating to commit 5b99eae59d59a8e34a7e512059b98bbd803312f2 today, I’m finding that it dies with a "Segmentation fault (core dumped)" in about 30 minutes or less.

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

If you have any advice on capturing more information about the segfault, let me know.

-Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20190107/11ccd02d/attachment.html>