public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: overseers@sourceware.org, elfutils-devel@sourceware.org
Subject: Moved elfutils.org to sourceware DNS
Date: Sun, 27 Aug 2023 14:36:07 +0200	[thread overview]
Message-ID: <20230827123607.GE8061@gnu.wildebeest.org> (raw)

Hi,

I moved elfutils.org to sourceware DNS. This shouldn't really impact
anything since elfutils.org is just a forward to
https://sourceware.org/elfutils/ It does make the https forward work
(previously only the http forward worked).

The debuginfod.elfutils.org server is run on elastic.org. I have added
an AAAA ipv6 record.

Technically this involved added an entry to /etc/named.conf on server2
and server3. The zone file is at /var/named/named.elfutils.org. The
forwards are in /etc/httpd/conf.d/sourceware-vhost-elfutils.conf. And
a new letsencrypt elfutils.org certificate was added with certbot.

Everything seems to work, but please let me know if you notice
anything wrong.

Cheers,

Mark

                 reply	other threads:[~2023-08-27 12:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230827123607.GE8061@gnu.wildebeest.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=overseers@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).