Mark:
We actually faced a similar problem (as far as inability to replicate to a
single machine - for other reasons than the arch). It's kind of a hokey
work-around, but it does work quite well, as long as you don't need it to be
instant.
** This would never be recommended for high-traffic servers, or servers
where updates to the db are taking place consistently.
On the primary nameserver, we dump the database to a SQL file which is made
available in a directory only readable by the IP address of the slave
machine. The file is pulled down from the master via HTTPS, and then
re-imported into the database on the slave - all done with a script.
We currently have our set up pulling the file every 7 minutes, which works
for us - but you may want to shorten or lengthen that timeframe.
Just out of curiosity - any reason you're using postgres instead of MySQL
for the pdns servers? MySQL replication works flawlessly cross-arch.
Chris Hesselrode | Principal / President
Phoenix Knowledge Ventures, LLC
PO Box 342
Maricopa, AZ 85139
-Original Message-
From: pdns-users-boun...@mailman.powerdns.com
[mailto:pdns-users-boun...@mailman.powerdns.com] On Behalf Of Mark Felder
Sent: Thursday, December 02, 2010 11:42 AM
To: pdns-users@mailman.powerdns.com
Subject: [Pdns-users] database backends without replication?
OK, well I have a small personal DNS infrastructure for some friends of mine
and myself and I wanted to use PowerDNS going forward. I have a few
questions though because I've never found clear information on this:
The servers are not the same arch; one is 32bit the other is 64bit. I want
to run a database backend (postgres) on at least one server so I can have
poweradmin. There's another server whichb can't receive the data by
streaming replication because of the arch difference and I'm not going to
screw with Slony or Londiste as a workaround. In our BIND setup at work, if
you have ns1 ns2 and ns3 and you add a domain, you have to actually modify
the config file on the ns2 and ns3 slaves before they will pick up the new
domain and records via AXFR. This is terribly tedious, and we actually rsync
ns2 to ns3 and trigger a reload as a workaround, but still it's lame. If I
use a database backend on each side without database replication, can I use
an AXFR to have it automatically add a domain to the database of the slave,
or is this still an issue with AXFR as a whole?
Simply put, I don't want to have to touch the slaves when a new domain is
added to the master. How does this work without database replication?
Thanks,
Mark
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
