[nSLUG] Looking for a DNS secondary partner
Eri Ramos Bastos
bastos.eri at gmail.com
Fri May 1 12:14:12 ADT 2009
It's a valid point of view, of course.
Maybe I like to live on the edge, but I've been using reiserfs for a
long time now and I never had any problems with any of the servers
and/or workstations deployed with that FS. And I'm not planing to
change my FS of choice until brtfs hits production or ZFS license
changes to make it compatible with GPL. Whatever cames first.
Same thing for DNS. After my research we did deployed PowerDNS and
it's working flawless since them. It's a recursive DNS only, so I
can't see many things going wrong here. And it's so easy to configure
that I don't keep a backup of it. If something happens and cripples
the server I just need to load a brand-new Linux image on the top,
install a single extra package and edit a 6 lines ascii file.
And that's the beauty of open source: choice. You have your
requirements, I have mine and still, both of us can find excellent
options to supply our needs.
Eri Ramos Bastos
> A few years back everyone seemed to be ready to hop
> on the reiserfs file system. I was ready to consider it as well,
> until the day I saw the help message for repairing the
> file system. It reminded me of the "send a cheque for $20
> to this address" type of software I used to see on tucows
> shareware in the 90's. Reiserfs struck me as amateurish for
> something corporations are about to adopt as best of breed.
> That alert message was a hint that this application
> depended on one developer.
> A few months later, the maker of Reiser FS was charged with
> murder, and today there doesn't appear to be a future
> for reiserfs.
> The lesson here is that performance isn't the only
> consideration in putting up services. You need to consider
> how many developers there are, whether the user base
> is large enough to shake out the bugs and security
> flaws, etc.
> Remember what Linus said : "given enough eyeballs, all bugs
> are shallow". This is why open source can be secure,
> despite revealing its inner workings. I prefer larger
> based projects for that reason.
> nSLUG mailing list
> nSLUG at nslug.ns.ca
More information about the nSLUG