[Pdns-users] problems with superslave pdns

[Anton - Valqk]

Hi there,
Eudene, maybe you have never heard of postgresql so you say it less tested.
rolf, this made my day :)
it's much more advanced database that 'text' mysql db. :) anywayz,
you misunderstood me,
the idea of my slave is to use the built in pdns functionallity,
not a db sync because the ns1 is a SLAVE vm machine, with ONLY 4
packages sqlite, pdns, iconv, gettext...

the whole idea is to use VERY simple backend there, because I must fit
in as low mem as I can.
so I can't affort to run a pg/my SQL server there.

I've tested pdns with both pgsql and mysql and it works like a chardm,
but I've never tested the supermaster feature, so I don't know how to debug,
no strange msgs in log when loglevel=14 ... just queries...
no idea how to solve the problem yet... please... anyone?

Eugene Pefti wrote:
> Hi Anton,
>
> PDNS forum seems to be not very active whenever one asks for help. Moreover there's a tendency to criticize people's questions not directly related to pdns such as the front-end to it. 
> Getting back to your question I can share my setup but it is not exactly like yours. I have MySQL backend and two servers configured to be master and slave. Having setup MySQL Master-to-Slave replication I have all changes introduced to the master via pdnsadmin replicate immediately to the slave, namely its database. 
> I don't think the replication between pgsql differs in terms of setup. I don't have much of experience with Postgresql so my suggestion is to switch to MySQL as it is more tested and often used. By the way I didn't have any problems with MySQL replication for two boxes located far from each other.
>
> Eugene
>
> -----Original Message-----
> From: pdns-users-bounces at mailman.powerdns.com [mailto:pdns-users-bounces at mailman.powerdns.com] On Behalf Of Anton - Valqk
> Sent: Monday, February 18, 2008 8:18 AM
> To: Pdns-users at mailman.powerdns.com
> Subject: [Pdns-users] problems with superslave pdns
>
> Hi there group,
> I've setuped a superslave pdns server that should fetch automatically 
> the newly added domains but nohting happens.
>
> my master is 217.75.141.6 and the slave dns is ns1.hostit.bg.
> I have this record for supermaster:
> sqlite> select * from supermasters;
> 217.75.141.6|ns1.hostit.bg|internal
>
> I've added a new domain into the master but it never showed up in the 
> logs or in the sqlite db.
> how can I debug why this happens?
> there is another problem,..
> I've inserted all the domains that were in the master pdns in the 
> records table, when I've first started the pdns it refreshed all the 
> domains,
> but after that from time to time I get:
> Feb 18 16:07:33 ns1 pdns[87710]: Domain interiorcity.net is fresh
> Feb 18 16:07:35 ns1 pdns[87710]: Error trying to retrieve/refresh 
> 'voigt-bg.com': Timeout waiting for answer from 217.75.141.6
> Feb 18 16:07:35 ns1 pdns[87710]: Domain arthotel-sbh.com is fresh
> Feb 18 16:07:35 ns1 pdns[87710]: Domain virtualboss.org is fresh
> Feb 18 16:07:36 ns1 pdns[87710]: Error trying to retrieve/refresh 
> 'radioyouth.eu': Timeout waiting for answer from 217.75.141.6
> Feb 18 16:07:36 ns1 pdns[87710]: Domain samsungwimax.com is fresh
> Feb 18 16:07:36 ns1 pdns[87710]: Domain bfc-bg.org is fresh
> Feb 18 16:07:36 ns1 pdns[87710]: Domain das.bg is fresh
> Feb 18 16:07:38 ns1 pdns[87710]: Error trying to retrieve/refresh 
> 'satelit-s.com': Timeout waiting for answer from 217.75.141.6
> Feb 18 16:07:39 ns1 pdns[87710]: Error trying to retrieve/refresh 
> 'globalestates.eu': Timeout waiting for answer from 217.75.141.6
> Feb 18 16:07:39 ns1 pdns[87710]: Domain profilexchange.org is fresh
> Feb 18 16:07:39 ns1 pdns[87710]: Domain 101dalmatinci.com is fresh
>
> I'm running powerdns-2.9.21 on both places, the os is freebsd.
> on the master side it's using pgsql backend on the slave it's psql 
> because the conectivity between the machines is not so good so I can 
> setup pgsql replication,
> and the second machine is  a vm with 1 purpose - slave dns.
>
> thanks in advance for the advices/ideas.
>
> cheers,
> valqk.
>
>   


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.