From: uhohspaghetios <uhohspaghetios@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dnsmasq: enable DNSSEC build option by default
Date: Wed, 26 Jun 2024 15:53:50 +0200 [thread overview]
Message-ID: <20240626135350.68E4F20218@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-50904@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
New comment by uhohspaghetios on void-packages repository
https://github.com/void-linux/void-packages/issues/50904#issuecomment-2191766843
Comment:
I am going to disagree with you there. I get this error when setting the dnssec option in dnsmasq.conf
> % doas dnsmasq -u dnsmasq -g dnsmasq
>
> dnsmasq: unsupported option (check that dnsmasq was compiled with DHCP/TFTP/DNSSEC/DBus support) at line 6 of /usr/share/dnsmasq/trust-anchors.conf
My dnsmasq.conf file:
`conf-file=/usr/share/dnsmasq/trust-anchors.conf
dnssec
strict-order
no-resolv
server=::1#53000
listen-address=::1
no-dhcp-interface=::1
bind-interfaces
no-hosts
cache-size=1000`
I took a look at the template file. I see the build option to build with DNSSEC support, but apparently that is not happening.
From the template:
`build_options="dnssec"
desc_option_dnssec="Enable DNSSEC support via nettle"`
next prev parent reply other threads:[~2024-06-26 13:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 17:48 [ISSUE] dnsmasq needs to be built with DNSSEC support uhohspaghetios
2024-06-23 11:08 ` dnsmasq: enable DNSSEC build option by default piekay
2024-06-26 13:53 ` uhohspaghetios
2024-06-26 13:53 ` uhohspaghetios [this message]
2024-06-26 13:54 ` uhohspaghetios
2024-06-26 14:05 ` classabbyamp
2024-06-26 15:23 ` [ISSUE] [CLOSED] " classabbyamp
-- strict thread matches above, loose matches on Subject: below --
2023-01-21 21:49 [PR PATCH] dnsmasq: enable dnssec " rvighne
2023-02-12 20:39 ` rvighne
2023-03-12 21:01 ` rvighne
2023-06-11 2:09 ` github-actions
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240626135350.68E4F20218@inbox.vuxu.org \
--to=uhohspaghetios@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).