Bind is the defacto DNS server out there, and the bind-dlz extensions enhances it even further by providing support for database backends. This simplifies the management of thousands of zones, and provides added redundancy (by way of database replication) and opens the doors for web frontends that ease this even more.
Bind DLZ on Rails is built based on our experience of managing thousands of DNS records through various (often crude) techniques, that included building zone files from databases via cron, and implementing PowerDNS for its database backends.
Nothing we tried seemed convincing, and we opted to go back to Bind using bind-dlz on a MySQL 5.0 backend. Using Rails 2 for a interface just makes sense because we can build a rich interface and an REST API in a single go.
This project is managed by Kenneth Kalmer.
As part of the PowerDNS on Rails project, and improving our own DNS infrastructure, I sat out today to configure 4 new DNS servers around the world. This will move a lot of our DNS traffic out of South Africa, while keeping some servers locally on the main networks (Internet Solutions & SAIX).
I rolled out [...]
It is with great excitement, and sadness that I announce the tag of BIND DLZ on Rails RC1.
We were very motivated as a team to get this product, and the accompanying infrastructure in place so would could continue to enhance and expand our DNS infrastructure. We made two fatal mistakes in trying to achieve this [...]
Just a quick update, we’re closing the gap rapidly on pushing RC1 to Github. Hopefully that happens by the weekend. We’ll also be rolling it into production use to iron out any last remaining issues that didn’t surface from our lab tests/reviews.
We just have one issue to overcome with will_paginate and our custom scoped finders [...]