This Week in Enterprise Tech

The DNS segment with Josh and Ross delivers a respectable volume of actionable concepts - RPZ, DDI team structures, encrypted DNS tradeoffs, namespace hygiene, GTLD collision risks - but total episode runtime is heavily diluted by three long ad reads, a superficial news blip section, and a multi-minute farewell segment. Per minute of actual technical content the density is reasonable, but per minute of total episode it is significantly lower.

“it's almost irresponsible to run any type of large scale enterprise DNS without some type of RPZ or DNS security mechanism there”

“by running your own encrypted DNS servers internally, you can actually see that traffic and then add those security controls back in”

The content is solid DNS practitioner education rather than genuinely contrarian or first-principles thinking; concepts like separating DNS from domain controllers, RPZ, DDI convergence, and encrypted DNS double-edged sword are standard in the DNS professional community. The nuclear plant and Korea TLD anecdotes add colour but don't reframe conventional wisdom.

“DNS is kind of the Rodney Dangerfield of network services”

“DNS might be someday to say that's it. No names will resolve except these names that we say are okay to resolve”

Josh Kuo and Ross Gibson are genuine practitioners - Josh did extensive consulting deployments and migrations, Ross spent seven-plus years as an enterprise DNS customer before joining Infoblox, and both co-authored a book specifically on DNS security. They are vendor employees however, which introduces some promotional framing, and the news blip segment lacks any expert input at all.

“I was actually a customer for, gosh, about seven and a half years before I came to Infoblox”

“I used to do a lot of deployments and migrations. So I've had a customer who felt like, well, I'm going to run DNS”

The episode earns its score with named real-world scenarios - the nuclear power plant DNS data leak, the Korea TLD purchase forcing a full re-architecture, the ship-based AD satellite latency problem - and specific technology names (RPZ, DOH, DOQ, DDI, SRV records). Missing almost entirely are dollar figures, scale metrics, or quantified business impact beyond one passing 'millisecond' claim.

“I have seen one where the customer is a nuclear power plant, so they're under a very strict set of regulations that they cannot reveal their internal networks”

“several years later that actually got bought by somebody in Korea and they had a huge concern just from a security perspective”

Brian Chee asks the more substantive questions - team reorganisation dynamics, the crystal ball on DNS direction, hybrid AD complexity - and they do draw out concrete anecdotes. However, the guests are from a sponsor-adjacent vendor (Infoblox) and face zero pushback on any claim; the farewell ceremony consumes the final 10-plus minutes and the host questions trend toward 'tell me more' rather than genuine challenge.

“What kinds of team mergers or splits are you starting to see in medium to large scale enterprises?”

“Where are we going? It sounds like there's a lot of things changing. I've been to several IETF meetings and talk about herding feral cats”