<div>PowerDNS can fork the process as many times as you configure using the distributor-threads option.</div><div><br></div><div>The good thing is the process remains running and kept running by PowerDNS's guardian so I think it will be more limited by your process than by PowerDNS :)</div>
<div><br></div><div>Re: Peter van Dijk</div><div><br></div><div>Thank you for that, I will check it out :) - right now I also read the openvpn ipp.txt file every time it changes to give vpn clients their own hostname so the pipe backend gives a bit more flexibility, but will definitely check out the remotebackend!</div>
<br><div class="gmail_quote">On 4 February 2013 09:39, RBK1001 <span dir="ltr"><<a href="mailto:Paul.Sun@syniverse.com" target="_blank">Paul.Sun@syniverse.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi<br>
<br>
Thank for the reply. If using pipebackend/bindbackend, is the performance<br>
acceptable when comparing within mysql/pgsql?<br>
<br>
- rbk<br>
<div><div class="h5"><br>
<br>
<br>
Roman Gaufman-2 wrote:<br>
><br>
> I really love the simplicity of pipe backend and why I use powerdns<br>
> instead<br>
> of say bind, all you need to really do is add this to your pdns.conf:<br>
><br>
> launch=pipe,bind<br>
> pipe-command=/etc/powerdns/dns_pipe.rb<br>
><br>
> And in your script, you can have something as simple as:<br>
><br>
> require 'powerdns_pipe'<br>
> PowerDNS::Pipe.new.run! do<br>
> answer :name => <a href="http://question.name" target="_blank">question.name</a>, :type => 'A', :ttl => 60, :content =><br>
> '1.2.3.4'<br>
> end<br>
><br>
> The above is an example written in Ruby, but really it just reads DNS<br>
> requests from STDIN and writes DNS responses to STDOUT. You can add any<br>
> custom code that will figure out the IP to your question - in my case I<br>
> plan to query a RESTFUL Rails API.<br>
><br>
> Roman<br>
><br>
> On 4 February 2013 09:29, RBK1001 <<a href="mailto:Paul.Sun@syniverse.com">Paul.Sun@syniverse.com</a>> wrote:<br>
><br>
>><br>
>> Hi<br>
>><br>
>> Thank for the information.<br>
>><br>
>> I have a bit confused on the the pipebackend and bind backend, which one<br>
>> should I use?<br>
>><br>
>> - rbk<br>
>><br>
>><br>
>> Ruben '_cyclops_' d'Arco wrote:<br>
>> ><br>
>> > Hi,<br>
>> ><br>
>> > This should be helpful as a first start:<br>
>> > <a href="http://doc.powerdns.com/backend-writers-guide.html" target="_blank">http://doc.powerdns.com/backend-writers-guide.html</a><br>
>> ><br>
>> > Also have a look at the regression-test direcory, as it is quiet helpul<br>
>> > for testing your backend.<br>
>> ><br>
>> > Regards,<br>
>> > Ruben<br>
>> ><br>
>> > RBK1001 <<a href="mailto:Paul.Sun@syniverse.com">Paul.Sun@syniverse.com</a>> wrote:<br>
>> ><br>
>> >><br>
>> >>Hi<br>
>> >><br>
>> >>we would like to seek for an advice on the use of backend.<br>
>> >><br>
>> >>we understood that PowerDNS offers several backend solutions, however,<br>
>> >>I<br>
>> >>would like to know is there a way to connect to our customerized<br>
>> >>backend?<br>
>> >>Currently, we are using a non-sql customerized backend with large<br>
>> >>amount of<br>
>> >>data stored, and we would like to intergrate powerdns with it, is there<br>
>> >>anyway we can do?<br>
>> >><br>
>> >>- rbk<br>
>> ><br>
>> > --<br>
>> > Regards,<br>
>> > Ruben<br>
>> > _______________________________________________<br>
>> > Pdns-users mailing list<br>
>> > <a href="mailto:Pdns-users@mailman.powerdns.com">Pdns-users@mailman.powerdns.com</a><br>
>> > <a href="http://mailman.powerdns.com/mailman/listinfo/pdns-users" target="_blank">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br>
>> ><br>
>> ><br>
>><br>
>> --<br>
>> View this message in context:<br>
>> <a href="http://old.nabble.com/PowerDNS-backend-tp34979116p34979385.html" target="_blank">http://old.nabble.com/PowerDNS-backend-tp34979116p34979385.html</a><br>
>> Sent from the PowerDNS mailing list archive at Nabble.com.<br>
>><br>
>> _______________________________________________<br>
>> Pdns-users mailing list<br>
>> <a href="mailto:Pdns-users@mailman.powerdns.com">Pdns-users@mailman.powerdns.com</a><br>
>> <a href="http://mailman.powerdns.com/mailman/listinfo/pdns-users" target="_blank">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br>
>><br>
><br>
> _______________________________________________<br>
> Pdns-users mailing list<br>
> <a href="mailto:Pdns-users@mailman.powerdns.com">Pdns-users@mailman.powerdns.com</a><br>
> <a href="http://mailman.powerdns.com/mailman/listinfo/pdns-users" target="_blank">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br>
><br>
><br>
<br>
--<br>
</div></div>View this message in context: <a href="http://old.nabble.com/PowerDNS-backend-tp34979116p34979413.html" target="_blank">http://old.nabble.com/PowerDNS-backend-tp34979116p34979413.html</a><br>
<div class="HOEnZb"><div class="h5">Sent from the PowerDNS mailing list archive at Nabble.com.<br>
<br>
_______________________________________________<br>
Pdns-users mailing list<br>
<a href="mailto:Pdns-users@mailman.powerdns.com">Pdns-users@mailman.powerdns.com</a><br>
<a href="http://mailman.powerdns.com/mailman/listinfo/pdns-users" target="_blank">http://mailman.powerdns.com/mailman/listinfo/pdns-users</a><br>
</div></div></blockquote></div><br>