nanog mailing list archives
Re: Slack.com DNSSEC on Feb 12th 15: 00 UTC
From: "John Levine" <johnl () iecc com>
Date: 4 Feb 2022 20:32:01 -0500
It appears that Peter Beckman <beckman () angryox com> said:
Agreed! Slack should probably move away from the custom domain model, and go with slack.com/w/bjornbjorn moving forward.
Their problem was poorly debugged software. I don't see any reason that web software is necessarily any better debugged than DNS software. I use DNSSEC signed wildcards and it works fine, although it has blown up the occasional buggy web spider which is not my problem. Check out https://www.web.sp.am. R's, John
On Fri, 4 Feb 2022, Christopher Morrow wrote:On Fri, Feb 4, 2022 at 10:54 AM Bj�rn Mork <bjorn () mork no> wrote:I assume you know which names you are going to serve?how would they be able to serve: footgun.slack.com bjornbjorn.slack.com ilovecorn.slack.com so immediately without that wildcard though?
-- Regards, John Levine, johnl () taugh com, Primary Perpetrator of "The Internet for Dummies", Please consider the environment before reading this e-mail. https://jl.ly
Current thread:
- Slack.com DNSSEC on Feb 12th 15:00 UTC Rafael Elvira via NANOG (Feb 04)
- Re: Slack.com DNSSEC on Feb 12th 15:00 UTC Bjørn Mork (Feb 04)
- Re: Slack.com DNSSEC on Feb 12th 15:00 UTC Christopher Morrow (Feb 04)
- Re: Slack.com DNSSEC on Feb 12th 15:00 UTC Peter Beckman (Feb 04)
- Re: Slack.com DNSSEC on Feb 12th 15: 00 UTC John Levine (Feb 04)
- Simplified BGP peering solution Josh Saul (Feb 07)
- Re: Simplified BGP peering solution Laura Smith via NANOG (Feb 07)
- Re: Simplified BGP peering solution Mike Hammett (Feb 07)
- Re: Simplified BGP peering solution Jon Lewis (Feb 07)
- RE: Simplified BGP peering solution Adam Thompson (Feb 07)
- Re: Slack.com DNSSEC on Feb 12th 15:00 UTC Christopher Morrow (Feb 04)
- Re: Slack.com DNSSEC on Feb 12th 15:00 UTC Bjørn Mork (Feb 04)
- Re: Slack.com DNSSEC on Feb 12th 15:00 UTC Shumon Huque (Feb 04)