news
5

A new write-up recounts the journey of replacing AWS Route53 with a self-run authoritative DNS server. It explores the motivations and challenges behind bringing DNS infrastructure in-house, despite DNS’s reputation as a common source of outages.

Only full members can comment

Log in to express your opinion.

No comments yet.