[Pdns-users] TinyDNS Backend questions

[Henry Paulissen]

Francois,

I am the user where cyclops refers to.
Altough im not exactly the user, I am the builder and tester of the
platform and maintained it for a while.

I had the same goals as you, get rid of /djbdns/ by moving to powerdns
with tinydns backend and after that
change tooling so we can move to a mysql backend. I also tested with
tinydns backend acting as master and
mysql backend as slave. This worked flawless altough it took some time
and load before all records where transferred.

For the records,
I ran tinydns backend about 3 months in production. I found some bugs in
the beginning, but they where adequately solved by cyclops (and his team
members).

As you can see I have some rich experience with the tinydns backend.

If you like, we can look if I can help you out on the office. I'm a
freelancer and always available for good assignments.
I suggest you contact me at my email address if you like the idea
(Business is not something for the maillist).



Regards,
Henry Paulissen


> Hi Francois,
> 
> ...
> 
> We know one user who uses it with a data.cdb file > 70M. That user also has identified some issues, one
> important issue is fixed in http://wiki.powerdns.com/trac/changeset/2622
> You can either apply the patch yourself, or take PowerDNS's SVN version to have this resolved.
> This patch is strongly recommended!
> 
> The scenario you're planning (move from dbjdns to powerdns and then change backend) is a scenario we've heard before 
> and partially why the backend was created - the master mode that the backend provides should help you with this.
> 
> 
> On Fri, Aug 31, 2012 at 09:53:58AM +0200, xbgmsharp wrote:
> >/ Hello,
> >
> > According to the documentation
> > (http://doc.powerdns.com/tinydnsbackend.html), the TinyDNS backend
> > is marked as experimental!
> > It this statement still true?
> >
> > We are currently using tinydns and djbdns in all our infrastructure.
> > We are thinking in moving to Powerdns to support new feature.
> > However before doing a big move, we would rater make the move in
> > multiple step.
> > The first step would be to use Powerdns with TinyDNS backend.
> > The second step would be to move from TinyDNS backend to a database
> > backend.
> > This second step require a rewrite of our DNS tools and it will take
> > longer.
> >
> > Our data.cdb is file is around 18M.
> >
> > Do you think it is safe to use Powerdns with TinyDNS backend in
> > production?
> >
> > Regards,
> > Francois
> >
> > _______________________________________________
> > Pdns-users mailing list
> > Pdns-users at mailman.powerdns.com
<http://mailman.powerdns.com/mailman/listinfo/pdns-users>
> > http://mailman.powerdns.com/mailman/listinfo/pdns-users










-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20120831/2609f6e6/attachment-0001.sig>