From: Jon Murphy <jon.murphy@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Proof of concept: Bridge rewrite of unbound-dhcp-leases-bridge
Date: Fri, 01 Dec 2023 00:36:21 +0000 [thread overview]
Message-ID: <170139098174.90119.1253631801385918485@mail02.haj.ipfire.org> (raw)
In-Reply-To: <170138447016.81511.7036801299375036151@mail02.haj.ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 612 bytes --]
It just dawned to me some of the things you mentioned and I may have this part wrong:
> - It appears Unbound is constantly monitoring this file. Unbound seems to recognize the changes and accept the > A and PTR records.
> - NOTE: I began my tests by manually entering file and they seem to be accepted fine.
> - NOTE: I still have testing to do to make sure this works properly!
> - NOTE: Unbound is the part that worries me the most since I don't understand why this works! I need to keep testing by removing/adding the unbound reload code in the existing bridge!
Back to the drawing board!
next parent reply other threads:[~2023-12-01 0:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170138447016.81511.7036801299375036151@mail02.haj.ipfire.org>
2023-12-01 0:36 ` Jon Murphy [this message]
2023-12-02 16:03 ` Jon Murphy
2023-12-08 16:26 ` jon
2023-12-19 22:34 ` jon
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=170139098174.90119.1253631801385918485@mail02.haj.ipfire.org \
--to=jon.murphy@ipfire.org \
--cc=development@lists.ipfire.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