On 01. 12. 21 12:07, Tim Wicinski wrote:
What I noticed in reading this nice write up was the warning image they
missed in the Route53 console
because of the automation they use. But most folks use
automation/tooling/etc in their workflow, and
catching those warnings via automation is a bit tricky.
Right after this happened several different teams looking to sign their
zones got a little nervous.
This writeup helps to show people how things can break, but also, there
is a great set of testing
methods to assist others.
Mark's comments about adding tests in DNSVIZ would be pretty great.
It is already implemented in DNSViz since December 2020 (so a year+
before the Slack outage), but it is not shown by default:
https://github.com/dnsviz/dnsviz/issues/76#issuecomment-985331543
--
Petr Špaček
_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
