From: Johannes Berg <johannes@sipsolutions.net>
To: David Young <dyoung@pobox.com>, radiotap@netbsd.org
Subject: Re: fyi: domains
Date: Mon, 20 Dec 2021 19:28:00 +0100 [thread overview]
Message-ID: <1fb03c68beeabe5db206e73410821b92c6906ea8.camel@sipsolutions.net> (raw)
In-Reply-To: <YcCzEnna1KGiQ1ax@pobox.com>
On Mon, 2021-12-20 at 10:45 -0600, David Young wrote:
> On Mon, Dec 20, 2021 at 10:31:13AM +0100, Johannes Berg wrote:
> > Hi Dave, all,
> >
> > On Wed, 2020-12-09 at 23:41 -0600, David Young wrote:
> > > I renewed radiotap.org for another year.
> > >
> >
> > Looks like it's been a year now and started being unavailable.
>
> Oops!
>
> I have renewed it, now. I got mixed up, thinking for some reason that
> radiotap.net was the name we had settled on. Sorry about that.
Oh, I thought you had released that one entirely.
Not that it would matter much.
> > Should we move off this entirely and just use the radiotap.github.io
> > name instead?
>
> I feel that $18/year for a "freestanding" domain is not a lot to pay for
> some independence from GitHub, should it ever be necessary or desirable
> to change hosting.
>
Thank you! I tend to agree, be willing to pitch in but I suppose quite
possibly at that low cost it's more expensive to figure out how to share
it...
FWIW, github now says:
radiotap.org is improperly configured
Domain does not resolve to the GitHub Pages server. For more
information, see Learn more (NotServedByPagesError). We recommend you
add an A record pointed to our IP addresses, or an ALIAS record
pointing to radiotap.github.io.
Still works for www.radiotap.org, so I guess all is well, and as before,
just that it complains now somehow.
(I didn't even know there was an "ALIAS" record, hah!)
Again, thanks!
johannes
prev parent reply other threads:[~2021-12-20 18:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 5:41 fyi: domains David Young
[not found] ` <2634cf7d1df09492d5a0e1610e3c0b4ba9cab7d4.camel@sipsolutions.net>
[not found] ` <YcCzEnna1KGiQ1ax@pobox.com>
2021-12-20 18:28 ` Johannes Berg [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=1fb03c68beeabe5db206e73410821b92c6906ea8.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dyoung@pobox.com \
--cc=radiotap@netbsd.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).