Comment 2 for bug 2015562
Revision history for this message
| Gordon G (vista-ubuntu) wrote Re: Segfault in dnsmasq when using certain static domain entries + DoH (bugfix possibly exists upstream) | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
After further testing, I can also see the crash occurs without with the `dns-no-doh.conf` config snippet loaded, even for a regular `A` record (so the TYPE65 query is also a red herring):
root@budgie:~# dig +short -tA test.netflix.net @127.0.0.1
root@budgie:~# dig +short -tA test.netflix.net @127.0.0.1
;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: connection refused
;; communications error to 127.0.0.1#53: connection refused
;; no servers could be reached
root@budgie:~# journalctl -fu dnsmasq
...
Apr 07 14:53:50 budgie dnsmasq[116972]: query[A] occ-0-4415-
Apr 07 14:53:50 budgie systemd[1]: dnsmasq.service: Main process exited, code=dumped, status=11/SEGV
Apr 07 14:53:50 budgie systemd[1]: dnsmasq.service: Failed with result 'core-dump'.
This further makes me think the commit I linked in my initial bug report is indeed the fix for this segfault.
The reproduction steps can be narrowed down to only using the netflix-nov6.conf configuration snippet, and performing a simple A record query on the subdomain of any of the domains listed in the snippet.
Coredump attached of the segfault during this simplified repro.