Hi,
I forgot to CC the list, here you find my latest answer to Stefan. It
still seems the configuration is OK, but that the PowerDNS master does
not start to notify my slaves on startup of new domains.
Domain: X.63.215.95.in-addr.arpa
I'm quite sure those settings are correct. I present the
Hi,
LikeFiction schreef:
Hi,
I forgot to CC the list, here you find my latest answer to Stefan. It
still seems the configuration is OK, but that the PowerDNS master does
not start to notify my slaves on startup of new domains.
snip
In my experience new domains added to the master need a
Good to have found someone with the same problem. Indeed a notify works,
but this is not what I want. I could automate it with a cronjob script,
but I think it might just be some bug in PowerDNS.
With kind regards / Met vriendelijke groet,
Pierre van den Oord
LikeFiction
Kleyn Proffijtlaan
On Aug 6, 2010, at 15:21 , LikeFiction wrote:
Good to have found someone with the same problem. Indeed a notify works, but
this is not what I want. I could automate it with a cronjob script, but I
think it might just be some bug in PowerDNS.
Really that shouldn't be necessary.
Can you show
On Aug 6, 2010, at 15:52 , LikeFiction wrote:
Stefan: As there is no sensitive information inside the tables, I have opened
up http://ns1.sologigabit.com/phpmyadmin with user help and password
help. You can browse all PDNS tables easily that way. For the mailing list
archive, I also
While i can not find anything that looks obviously wrong to me, you
might try the following:
- setting domains.notified_serial to 0 or 1.
- providing a full set of ttls in the SOA record such as
ns1.sologigabit.com. info.sologigabit.com. 2010080500 10800 3600 604800
3600
After stopping
On Aug 6, 2010, at 17:00 , LikeFiction wrote:
Ok, I think I found the problem. It's quite simple too.
My zones are not changing very often. So, after my re-setup of NS2, and
restart master-powerdns, the notified-serial and the first digit serial of
SOA where the same. If notified-serial
Need to add one thing:
I got put off by thinking you were provisioning a new zone and thus assuming
that notified-seriel would be set to 0 or NULL by default.
You where in fact for a part correct. By using Poweradmin (some time
ago), I created a new zone. Poweradmin however makes a soa
Hi all,
(Text-version instead of previous HTML, sorry for that)
I am having this problem for quite some time now. I have rechecked the
configuration many times, but I'm confident it is accurate. I have
installed two nameservers, ns1.domain.com and ns2.domain.com. The first
is a super-master
On Thu, Aug 05, 2010 at 03:55:24PM +0200, LikeFiction wrote:
and one row on supermasters table on slave:
ip: 95.215.63.212
nameserver: ns2..com (refers to slave itself)
Please read section 13.2.1. of
http://doc.powerdns.com/slave.html#SUPERMASTER
very slowly and carefully.
I would
10 matches
Mail list logo
