nanog mailing list archives
Re: Slack.com DNSSEC on Feb 12th 15:00 UTC
From: Bjørn Mork <bjorn () mork no>
Date: Fri, 04 Feb 2022 16:54:13 +0100
RFC1912 says Wildcard As and CNAMEs are possible too, and are really confusing to users, and a potential nightmare if used without thinking first. You know the nightmare is real. You've been there. So why the heck do you insist on keeping that wildcard? Nobody else use wildcard A records. There is no reason. It's a loaded footgun. I assume you know which names you are going to serve? Bjørn
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)