public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@elastic.org>
To: Ian Lance Taylor <ian@airs.com>
Cc: overseers@sourceware.org
Subject: sourceware dns tweaks
Date: Wed, 29 Apr 2020 10:36:52 -0400	[thread overview]
Message-ID: <20200429143652.GA193756@elastic.org> (raw)
In-Reply-To: <m3ftgfrswy.fsf@pepe.airs.com>

Hi, Ian -

Could you work with the DNS/registry data for sourceware.org to reset
the glue/delegation records?  These are sometimes called "registered
nameservers".  The .org zone includes glue records with the old IP
addresses of sourceware, and those need to get refreshed.

This is related to the warnings/errors indicated by a run of this:
https://dnsviz.net/d/sourceware.org/analyze/

Thanks!

- FChE

  parent reply	other threads:[~2020-04-29 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16 16:47 Resetting ssh publickey? Paul Murphy
2020-01-16 21:30 ` Ian Lance Taylor
2020-01-17 14:33   ` Paul Murphy
2020-01-30 17:41     ` Paul Murphy
2020-01-30 21:09       ` Frank Ch. Eigler
2020-04-29 14:36   ` Frank Ch. Eigler [this message]
2020-04-29 16:32     ` sourceware dns tweaks Ian Lance Taylor

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=20200429143652.GA193756@elastic.org \
    --to=fche@elastic.org \
    --cc=ian@airs.com \
    --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).