Show Notes
As DNS is more widely used to distribute certificate information, proving ownership of a resource becomes more critical. The constant challenges required to prove resource ownership, however, increase delay in connecting or using a resource. DNS persists--as the name implies--creates a persistent connection between a resource and a certificate authority. Henry Birge-Lee, Michael Slaughter, and Shiloh Heurich join Russ and Tom to explain how this new record type works and it's importance to DNS.
More from The Hedge
Network engineers do not need to become full-time coders to succeed--but some coding skills are really useful. In this episode of the Hedge, David Barrosso (you can find David's github repositories here), Phill Simonds, and Russ White discuss which programming skills are useful for network engineers.
Just about everyone is watching the financial markets, either wondering how much better they can get, or when the AI financing bubble is going to crash. Dough Dawson, from POTs and PANs, joins Tom and Russ to talk about the logic of a coming crash, and consider where engineers should be looking for potential future career fields to weather the storm.
There are many "unsung technologies" in the Internet. While we often think of TCP/IP, various models, Ethernet, and DNS, we don't often think about the lowly socket interface. What is the history of the socket, and why is it important in the world of the Internet? George Michaelson joins Colin Doyle and Russ White to discuss the history and importance of sockets.
Over time, services like DNS and email have been centralized, leaving the Internet itself much more centralized. In this episode of the Hedge, Doug Jacobson joins Tom Ammon and Russ White to discuss centralization and service consolidation.
AI is everywhere. While there are many questions about whether AI is a bubble, the ethics of AI, and the cultural impact of AI, in this episode of the Hedge Mike Bushong joins Eyvonne, Tom, and Russ to talk about how network engineers can use AI. Are some use cases better than others? Are there pitfalls network engineers should avoid? Listen in and find out.