[Pdns-users] Different MySQL server for reads vs writes

[Edward Dore]

You could also accomplish this with something like ProxySQL or MariaDB MaxScale sitting between PowerDNS and MySQL in order to transparently handle the read/write splitting if you wanted to only have a single PowerDNS instance for whatever reason.


Edward Dore

Freethought Internet

________________________________
From: Pdns-users <pdns-users-bounces at mailman.powerdns.com> on behalf of Chris <lists+pdns at gbe0.com>
Sent: 08 July 2019 06:25:04
To: pdns-users at mailman.powerdns.com
Subject: Re: [Pdns-users] Different MySQL server for reads vs writes

Hi,

I do this by creating a separate instance of PowerDNS for writes. As an
example, in /etc/powerdns I have:

pdns-internal.conf - Configured to use the read only database (listening
on port 5350 with no web server/API - queries are sent to it via dnsdist)
pdns-api.conf - Configured to use the write database (listening on port
5351 and the API/web server on 8351)

And I use the systemd service instances to manage this (eg.
pdns at internal, pdns at api)

On 8/07/2019 1:17 pm, Daniel Lo Nigro wrote:
> Is there a way to configure PowerDNS + the MySQL backend to send writes
> (eg. via the API) and reads to different servers? For example, if I want
> writes to always go to a master server, but reads to go to a slave.
>
> Thanks!
>
> _______________________________________________
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
> https://mailman.powerdns.com/mailman/listinfo/pdns-users
>
_______________________________________________
Pdns-users mailing list
Pdns-users at mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20190708/30194e8e/attachment.html>