Hi Atha,
Just though I would add that this is exactly how we do things where I work, but
with an additional layer that may or may not be necessary for you.
We have our slaves behind load balancers (Nortel Alteon's in our case) that can
do UDP session balancing so that there is literally no down
On 10 Nov 2010 wk 45, at 17:53, Atha Kouroussis wrote:
> Thanks everybody for you responses. This is what we are going for in our
> final deployment:
>
> - A master MySQL database holding all the domains. This is the database the
> provisioning system talks to
> - n PowerDNS servers with their
It looks like you are going to have two different
architectures/environments, one with automatic replica for internal
usage, and one with network replica for customers needing only a
secondary nameserver.
Personally, I would keep two separated architectures.
Cheers,
Tonino
Il 10/11/2010 17:
Thanks everybody for you responses. This is what we are going for in our final
deployment:
- A master MySQL database holding all the domains. This is the database the
provisioning system talks to
- n PowerDNS servers with their local MySQL database acting as slave of the
master database
- A sep
I don't know what other people think about this, but I was planning for
our deployment to have a pdns server with a MySQL backend that would be
private (nobody can query it directly) and then have our other DNS servers
that receive updates from it use a file backend because it's less
compli
Atha,
Indeed I must not have understood you quite properly. Why would you need even
need slave updates and/or master-master replication? The various PDNS servers
in this setup are all acting independently without any knowledge of each other.
They are all neither masters nor slaves, depending on
On 10 Nov 2010 wk 45, at 16:14, Atha Kouroussis wrote:
> Hi Nick,
> thank you for your quick answer!
>
> Obviously I didn't make myself clear in my email, since the second scenario
> we are contemplating, is very similar to what you described: one master
> backend, and then each pdns server ea
+1 for this configuration and +1 for the excellent writeup :)
On 11/10/2010 05:01 PM, Nick Williams wrote:
> Atha,
>
> Let me share with you what we did at the company I used to work for (and
> this is an identical configuration to what I have setup for myself). We
> don't have master and slave
Hi Nick,
thank you for your quick answer!
Obviously I didn't make myself clear in my email, since the second scenario we
are contemplating, is very similar to what you described: one master backend,
and then each pdns server each with its own slave backend. And I do see the
advantages in robust
He Atha,
We did the name thing Nick did, and I have two recommendation to his
(excellent) writeup:
* we do have one pdns that talks directly to the mysql master. The reason is
that we offer backup dns services for some customers that have their own
primary dns server. We use the supermaster fe
Atha,
Let me share with you what we did at the company I used to work for (and this
is an identical configuration to what I have setup for myself). We don't have
master and slave PDNS servers. We have "workers" of sorts. Our master and
slaves are the MySQL backends.
We have a master MySQL serv
Hi all,
we are looking to migrate from bind to PowerDNS with MySQL backend. Our initial
tests have gone really well and we are now looking into finalizing the
architecture for the final deployment and migration. In that respect we have a
couple of doubts.
Since we are going to be using the MySQ
12 matches
Mail list logo
