# powerdns Published articles for powerdns. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Who Controls the Internet? And should they? DevFeed: [Who Controls the Internet? And should they?]() Original publisher: [Read original article]() Published: 2021-11-02T14:02:51Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [Internet](), [intelligence](), [Open Source](), [powerdns]() Tags: [internet](), [open-source](), [powerdns](), [privacy](), [youtube]() ### AI overview A lightly edited transcript of a NANOG 83 keynote examining who influences the internet, including governments, companies, infrastructure operators, and protocol-level actors. The speaker defines a broad scope focused on who affects internet access, speed, and cost, while drawing on experience in open-source development and government work. ### Source excerpt This is a lightly edited transcript of my keynote over at NANOG 83, so please accept my apologies if some of the wording is not (yet) as clear as it should be! The original video, including Q&A can be found on NANOG's Youtube channel Hello, and welcome to this presentation on who controls the internet, and if they actually should. As you can see, I cover all grounds here. All kinds of flags are in this presentation and all kinds of companies. ## History of PowerDNS 2013-2020, part 3b: the business story DevFeed: [History of PowerDNS 2013-2020, part 3b: the business story]() Original publisher: [Read original article]() Published: 2021-04-21T16:07:06Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [Open Source](), [Software](), [Network]() Tags: [business](), [history](), [open-source](), [powerdns]() ### AI overview This article recounts PowerDNS's business history from 2013 to 2020, including its merger with Open-Xchange and changing customer-support challenges. It describes how the company served open source users publicly while providing dedicated support and feature work for commercial customers, as telecommunications companies increasingly outsourced network operations. ### Source excerpt This part of the history of PowerDNS is mostly about our business adventures & merger with Open-Xchange. The technical history of this period is described in part 3a. Business In 2013, PowerDNS was in a crucial phase. Existing business was going well, but we were receiving pointed signals there was trouble on the horizon. Some existing customers were close to deserting us, because we could not provide them with the top-down attention other vendors were lavishing on them. ## History of PowerDNS: 2013-2020 (Technology) DevFeed: [History of PowerDNS: 2013-2020 (Technology)]() Original publisher: [Read original article]() Published: 2020-12-21T19:32:58Z Content type: article Language: en Sources: [Bert Hubert's writings]() Topics: [Software](), [Software Engineering](), [domain](), [DNSSEC](), [ASCII](), [Protocol (disambiguation)]() Tags: [ascii](), [bugs](), [business](), [cleanup](), [cognitive-load](), [complexity](), [dns](), [dnssec](), [domain](), [history](), [powerdns](), [protocol](), [software](), [standards](), [technology]() ### AI overview This article covers the technical development of PowerDNS from 2013 to 2020, including an extensive internal cleanup of mature code. It explains how the cleanup addressed accumulated complexity, bugs, and incorrect treatment of DNS names as ASCII strings, including ordering, case, escaping, and spaces. ### Source excerpt In this part of the history of PowerDNS, I talk about the technical developments from 2013 to 2020. Over these years many fascinating business & hiring developments also happened, but these are described in a separate post, part 3B of the PowerDNS History. Here are the earlier parts: Part 1, Part 2 For context, the 2013-2020 era is what I would describe as "PowerDNS 3.0" - how we grew from a one (or two) person company to a healthy and thriving department of Open-Xchange. ## History of PowerDNS: 2003-2013 DevFeed: [History of PowerDNS: 2003-2013]() Original publisher: [Read original article]() Published: 2020-11-29T15:24:11Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [powerdns](), [Open Source](), [Job](), [intelligence]() Tags: [business](), [history](), [open-source](), [powerdns]() ### AI overview Part two of a retrospective history of PowerDNS covering the period from 2003 to 2013. The author recalls PowerDNS becoming dormant as a company while its open-source software continued to thrive, and describes later learning web technologies and joining the Dutch General Intelligence and Security Service. ### Source excerpt This is part two of the PowerDNS history as I recall it. As noted in part one, some of this stuff is rather old, and it is entirely possible I am misremembering things. Please do let me know if you find any important omissions or mistakes! At the end of 2002, beginning of 2003, PowerDNS as a going concern was gone. There were no more employees, there were no paying customers. ## History of PowerDNS: 1999-2003 DevFeed: [History of PowerDNS: 1999-2003]() Original publisher: [Read original article]() Published: 2020-11-27T11:29:55Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [powerdns](), [Internet](), [Authentication](), [Authorization](), [Monitoring](), [Redirection](), [service](), [Users]() Tags: [authentication](), [authorization](), [business](), [dns](), [history](), [internet](), [monitoring](), [powerdns](), [redirection](), [service](), [users]() ### AI overview The author recounts the early history of PowerDNS from 1999 to 2003, explaining how work at Casema Internet and later business experiences shaped its launch. The author notes that the account may contain forgotten or misremembered details. ### Source excerpt Hi everyone, I have often told the history of PowerDNS, or at least how I recall it, during talks and presentations. As I am about to truly leave DNS and PowerDNS, I thought it was high time to document my recollections. Since this is a 20+ year old story right now, it is very possible I have forgotten or misremembered important things. Do let me know if you miss important things, or if you recall things differently! ## Tracing App Backend Development DevFeed: [Tracing App Backend Development]() Original publisher: [Read original article]() Published: 2020-04-14T18:00:22Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [tracing](), [backend-development](), [API](), [Authorization](), [Scalability](), [Availability]() Tags: [api](), [authorization](), [availability](), [backend](), [github](), [high-scalability](), [open-source](), [powerdns](), [tracing]() ### AI overview The post discusses a Dutch government tender for privacy-sensitive Corona contact tracing technologies and a submitted proposal to build an open-source, scalable backend. The proposed backend would let apps query infected keys and authorized health care professionals submit them, with features including rollback, authorization checks, checkpointing, incremental updates, DoS filtering, high availability, and geo-redundancy. ### Source excerpt bert@hubertnet.nl / @bert_hu_bert / LinkedIn Very quick post. The Dutch government just launched a tender for "digital technologies that can help with Corona". The tender includes words on privacy sensitive contact tracing, it explicitly refers to PEPP-PT, the Pan-European Privacy-Preserving Proximity Tracing project. Responses are due on Tuesday the 14th of April, 12:00 (noon). The question/answer form asks if you can do a demo on the 18th of April and have something that could be rolled out on the 28th. ## A 2019 update on PowerDNS, Galileo, DoH and other things DevFeed: [A 2019 update on PowerDNS, Galileo, DoH and other things]() Original publisher: [Read original article]() Published: 2020-01-01T14:37:52Z Content type: article Language: en Sources: [Bert Hubert's writings]() Topics: [powerdns](), [Internet](), [Programming]() Tags: [diary](), [dns](), [gnss](), [lua](), [powerdns](), [privacy](), [programming]() ### AI overview A 2019 professional update covering the author's work on PowerDNS, DNS over HTTPS, Galileo, and related community and advisory activities. The article also explains that the PowerDNS team had taken full responsibility for day-to-day management and technical decisions. ### Source excerpt Last year I wrote a post listing what I had been doing in 2018, because it turned out it was a lot, so much that it was useful to summarise it somewhat. This year there is less to report, but people have wondered what I've been up to. And I've learned that if you leave room for speculation about your intentions, wrong answers tend to come up. This (professional) year for me mostly consisted of two things: DNS over HTTPS and Galileo. ## PowerDNS After Its Transition to Open-Xchange and Concerns About Email Centralization DevFeed: [PowerDNS After Its Transition to Open-Xchange and Concerns About Email Centralization]() Original publisher: [Read original article]() Published: 2018-12-30T13:26:04Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [powerdns](), [Open Source](), [email](), [Internet]() Tags: [diary](), [email](), [internet](), [liberty-global](), [open-source](), [personal](), [powerdns]() ### AI overview A personal account of PowerDNS after its transition to Open-Xchange, including the shift of day-to-day management to professional staff and the author's broader role. The article also argues that email has become less open because dominant providers can reject messages from smaller servers without explanation or recourse. ### Source excerpt This is a more personal post than I usually write, and it was prompted by several people asking what I had been up to lately. It turns out that it is somewhat of a story. It is a long story too. Since the beginning of 2018 day to day management of PowerDNS is now truly in the hands of professionals. I'm very proud to report that PowerDNS has not only survived the transition to Open-Xchange but is actually thriving & has achieved sufficient revenues & talented staff that we've solved the famous open source "what if Bert gets hit by a bus" problem.