From: Ian Lance Taylor <ian@airs.com>
To: "Frank Ch. Eigler" <fche@elastic.org>
Cc: overseers@sourceware.org
Subject: Re: sourceware dns tweaks
Date: Wed, 29 Apr 2020 09:32:45 -0700 [thread overview]
Message-ID: <m3zhauntg2.fsf@pepe.airs.com> (raw)
In-Reply-To: <20200429143652.GA193756@elastic.org> (Frank Ch. Eigler's message of "Wed, 29 Apr 2020 10:36:52 -0400")
"Frank Ch. Eigler" <fche@elastic.org> writes:
> 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/
Everything should be updated now, though I'm not sure how long it will
take to propagate. Let me know if you see any problems.
Ian
prev parent reply other threads:[~2020-04-29 16:33 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 ` sourceware dns tweaks Frank Ch. Eigler
2020-04-29 16:32 ` Ian Lance Taylor [this message]
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=m3zhauntg2.fsf@pepe.airs.com \
--to=ian@airs.com \
--cc=fche@elastic.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).