I ran into an obscure limitation in PowerDNS 4.0 authoritative server recently. I have one nameserver which also acts as a slave to two other sets of zones with are transfered using AXFR. Some of those zones are DNSSEC enabled, and PowerDNS is only able to handle DNSSEC on the first backend loaded. This was causing several forward and reverse zones to fail to serve the DNSSEC records along with the queried records, and DNSSEC validation to partially fail.
PowerDNS makes a mighty fine authoritative, and also recursive DNS server. They also recently added a DNS-aware DNS load balancer. This article deals with load balancing multiple backend caches to keep all of them hot and working the most efficiently.
Building a Slack /bgp slash command using custom API at api.hextet.net: integrating BGP lookups, whois, and looking glass functionality directly into Slack channels via web API POST integration.
VMware ESXi 6.0 Update 2 improvements: using HTML5 VMware Host Client for full VM provisioning without Windows vSphere client, functional browser-based console, fixed macOS Remote Console launching, and no Flash required for administration.
I first came across dnsdist in a NANOG post in the discussion of exploitation of a BIND DOS bug last summer. Jared Mauch had recommended dnsdist to easily implement DNS backend diversity.
