On Sat, Oct 2, 2021, at 14:52, Sebastian Benoit wrote:
> abyx...@mnetic.ch(abyx...@mnetic.ch) on 2021.10.01 09:56:32 -0400:
>> On Fri, Oct 1, 2021, at 09:44, Stuart Henderson wrote:
>> > On 2021/10/01 14:43, Stuart Henderson wrote:
>> >> On 2021/10/01 09:29, abyx...@mnetic.ch wrote:
>> >> > I'm
On Fri, Oct 1, 2021, at 09:44, Stuart Henderson wrote:
> On 2021/10/01 14:43, Stuart Henderson wrote:
>> On 2021/10/01 09:29, abyx...@mnetic.ch wrote:
>> > I'm getting a daily crash (call to fatalx). No clue what triggers it and
>> > the logging is really sparse. I couldn't follow what the code
I'm getting a daily crash (call to fatalx). No clue what triggers it and the
logging is really sparse. I couldn't follow what the code in ca.c is actually
doing (what the hash belongs to that is triggering the crash). A snip from
/var/log/daemon is reproduced below. There are no other log
On Tue, Sep 28, 2021, at 11:22, Brian Brombacher wrote:
>> On Sep 27, 2021, at 8:52 PM, abyx...@mnetic.ch wrote:
>>
>> Hello, trying to set up unwind with nsd on the same machine serving a
>> internal domain (home.arpa) with all my machines being part of that domain,
>> eg router.home.arpa. If
On Tue, Sep 28, 2021, at 06:25, Paul de Weerd wrote:
> Hi,
>
> Why do you set your NSD as a forwarder? How is unbound supposed to
> know what queires should go to your NSD versus the rest of the
> internet?
Thanks Paul and Otto. I chose NSD here because it looked much easier than
unbound to set
Hello, trying to set up unwind with nsd on the same machine serving a internal
domain (home.arpa) with all my machines being part of that domain, eg
router.home.arpa. If I point dig at my nsd instance (dig @127.0.0.1 -p 10053
router.home.arpa. A) I see my subdomains in the zone all being
