<story><title>Migrating Mess with DNS to Use PowerDNS</title><url>https://jvns.ca/blog/2024/08/19/migrating-mess-with-dns-to-use-powerdns/</url></story><parent_chain></parent_chain><comment><author>benreesman</author><text>I’ve said similar before but I’m just so impressed with Julia Evans as a technologist and technology writer&amp;#x2F;blogger: from very humble beginnings the scope and sophistication and arc of growing expertise is a masterclass in how to become a legend via putting in the work: and in an age of so many bytes on how to take shortcuts this is exactly the kind of role model we need.&lt;p&gt;In this particular instance I recall the post about DNS some years ago and the callback is amply enriched.&lt;p&gt;Keep it up @jvns. You hold us all to a high standard.</text></comment>
<story><title>Migrating Mess with DNS to Use PowerDNS</title><url>https://jvns.ca/blog/2024/08/19/migrating-mess-with-dns-to-use-powerdns/</url></story><parent_chain></parent_chain><comment><author>joeig</author><text>&amp;gt; Sometimes users will still get errors from PowerDNS directly, but I added some logging of all the errors that users see, so hopefully I can review them and add extra translations if there are other common errors that come up.&lt;p&gt;I noticed that you are using our Go module to access the API. It is wonderful to see our work helping others build great software, especially for education. Thank you for that.&lt;p&gt;Please note that the upstream API sometimes changes slightly between minor releases. For example, prior to v4.9, the error response for a non-existent server was &amp;quot;Not Found&amp;quot;. Starting with v4.9, it changed to &amp;quot;Method Not Allowed&amp;quot;.&lt;p&gt;Unfortunately, error responses aren&amp;#x27;t always part of the API specification. I&amp;#x27;m thinking about adding the most common cases to the module anyway.</text></comment>