- PowerDNS was dormant with no revenue from 2002–2003, leading the founder to explore new skills like HTML and briefly work for the Dutch intelligence service (AIVD) while continuing open-source development.
- A critical bug in 2004 using an incorrect future date caused the authoritative server loop to wake thousands of times per second, breaking installations and disrupting a personal event.
- The PowerDNS Recursor was developed using a userspace cooperative multitasking system to handle DNS resolution linearly, addressing complexity issues found in BIND and dnscache.
- XS4ALL paid €7,000 in 2005 to make the Recursor production-ready, enabling scaling for large ISPs like AOL, which decommissioned 120 servers using the improved software.
- A scaling issue with CPE routers misinterpreting DNS compression markers ('C0 0C') highlighted problems only seen at high volumes, leading to optional DNS features becoming mandatory.
- Wikipedia contributed code for geographical load balancing and label compression, fulfilling an original PowerDNS goal that had been delayed until later Lua record implementation.
- From 2007, Nominum's aggressive pricing drove customers like Liberty Global and Shaw Cable to migrate to PowerDNS, emphasizing the risk of selling cheaply to large companies.
- Maintaining the company's optical presence (website, releases, support) with zero revenue for years built credibility, proving no shortcuts to becoming an established vendor.
- Directi's CEO pushed for performance improvements in 2008, leading to a redesigned authoritative server, though dnsdist later fully met their needs.
- Deutsche Telekom's 2008 request for dynamic DNS filtering (linked to Ursula von der Leyen's anti-child-pornography initiative) led to Lua scripting integration, securing a major support contract that shifted PowerDNS financially.
- DNSSEC adoption was simplified in 2010 via a 'one-switch' approach, aided by SIDN incentives, resulting in over half of .NL domains becoming secure.
- PowerDNS monetized open source by selling 'reassurance' (procurement credibility and 24/7 support) rather than code, leveraging community contributions for cost efficiency.
- Exceptional support ('total support') fixed non-PowerDNS issues (e.g., Linux IPv6 scaling bugs), building customer trust beyond typical vendor support.
- Peter van Dijk joined in 2011, migrating to GitHub, enabling major community contributions like RFC 2136 support, but the two-person company faced growth pains from limited capacity and no office.
- Faking an office for a client visit with a temporary PowerDNS logo highlighted challenges in competing with vendors like Cisco, as top-down sales and integration demands threatened the old support-only model.