From: Chris Marusich <cmmarusich@gmail.com>
To: Julien Lepiller <julien@lepiller.eu>
Cc: guix-devel@gnu.org
Subject: Re: guix.gnu.org sub-domain
Date: Mon, 08 Apr 2019 18:48:02 -0700 [thread overview]
Message-ID: <8736ms3q5p.fsf@gmail.com> (raw)
In-Reply-To: <0E8676FF-2F46-48FA-8B36-33DFF6812032@lepiller.eu> (Julien Lepiller's message of "Mon, 08 Apr 2019 15:22:44 +0200")
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
Hi Julien,
Thank you for working on this!
Julien Lepiller <julien@lepiller.eu> writes:
> I'm still unsure about how to update the certificates with the dns
> challenge. I found a script that could help us with updating the zone
> served by knot when it's configured as a master.
>
> We could use that to update the required txt record, but we also need
> to make sure the change is propagated to the other server, because we
> don't know which server will be asked to answer the challenge.
>
> With a further delegation of the record for the dns challenge we can
> have two masters, but I'm still stuck at finding a way to communicate
> the challenge between the two servers.
>
> Ideas?
Can we update the DNS dynamically [1]? Can you share the script?
I still don't know as much about Knot as I should, but I'm surprised
that a change to the primary server's database would not be propagated
to the secondary server's database automatically. Can you elaborate on
what goes wrong, or maybe explain (even at a high level) how I can try
reproducing the problem with cert renewal locally?
Footnotes:
[1] https://tools.ietf.org/html/rfc2136
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-04-09 1:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 12:38 guix.gnu.org sub-domain Ricardo Wurmus
2019-04-08 8:59 ` Ludovic Courtès
2019-04-08 13:22 ` Julien Lepiller
2019-04-09 1:48 ` Chris Marusich [this message]
2019-04-09 8:32 ` Julien Lepiller
-- strict thread matches above, loose matches on Subject: below --
2018-12-03 15:43 [PATCH 0/3] Defaulting to ci.guix.info (aka. berlin.guixsd.org) Ludovic Courtès
2018-12-03 16:12 ` Using a CDN or some other mirror? Ludovic Courtès
2018-12-09 3:33 ` Chris Marusich
2018-12-09 15:59 ` CDN performance Ludovic Courtès
2018-12-13 8:05 ` Chris Marusich
2018-12-14 10:26 ` guix.gnu.org sub-domain Ludovic Courtès
2018-12-15 23:20 ` Chris Marusich
2019-01-25 4:54 ` Amin Bandali
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8736ms3q5p.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).