[Pdns-users] Question about Powerdns remote database backend best practices

Thomas Mieslinger miesi at mail.com
Tue Nov 17 14:56:15 UTC 2020

The way to scale is to have a config management that allows easy setup
of many servers running the MySQL + PDNS Stack.

On 11/17/20 10:47 AM, Jianan Wang via Pdns-users wrote:
> Hi there,
> Recently I’m trying out PowerDNS, and I’m pretty enjoy the flexibility
> and abundant API and Powedns admin UI compared to our regular bind
> deployment. I’m currently using a remote MySQL as backend to serve the
> request, and as recommended by the wiki, I use IP to avoid the
> Chicken-Egg problem when using DNS.
> However, one thing I’m wondering is that how to make this ip based
> remote backend solution more production ready. From what I have read on
> many tutorials online, most of the MySQL database are set up locally,
> which I think is good for POC, but local is not scalable and easy to
> manage when database entries scale up. However, if we use ip based
> solution, normal corp database deployment will have master and slave,
> and it is hard to manage if we hardcode an ip, which is subject to
> change from master to slave or vice versa, in the config.
> Any suggestion or comment is welcomed. Thanks in advance.
> Best regards.
> Jianan.
> --
> Jianan Wang
> _______________________________________________
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
> https://mailman.powerdns.com/mailman/listinfo/pdns-users

More information about the Pdns-users mailing list