Warning: spoiler alert!  Do not listen to this episode if you do not want to learn the identity of the final Cylon in Battlestar Galactica.  Also, do not listen if you do not want to hear Matt correct and elaborate a bit on DNSSEC topics from Episode 2.  And especially do not listen if you are not interested in learning about the uses of stub zones and hearing an explanation of web browser DNS “pre-fetching”.  Otherwise, it’s fine to listen and we hope you will.

>> Listen

Read more...

In our second episode, Matt and Cricket discuss Matt’s distaste for handbells and lapse into a discussion of Star Trek (The Original Series) — oh, and answer an actual listener’s question about when DNSSEC deployment will be widespread.  Also, Cricket says “Right, right” many times.

>> Listen

Read more...

I subscribe to the fundamental tenets of Greg Ness's Infrastructure 2.0 postulate:  That core network services will become more strategic, and that these services must become more dynamic and better automated to support next-generation information technology.  But every time I read about Infrastructure 2.0, I worry about DNS and the other protocols that underpin our networks.

These protocols, as nearly everyone knows, were designed in the Dark Ages of the Internet, before DHCP and WiFi and Dan Kaminsky.  It's a tremendous credit to the adaptability and scalabilty of their original designs that DNS and its kin can support today's global Internet.  At the same time, it's required a small army of dedicated protocol engineers working within the IETF to create the modern version of DNS, with its dynamic updates and signed zone transfers.

Read more...