[Pdns-users] NOTIFY FAILURE!

[Ale *****]

Hello to all,
I'm a newbie about PowerDNS. On a first machine (192.168.0.1) I have PowerDNS act as master that use mysql(gmysql) backend and on another machine (192.168.0.2)
bind9 act as slave. So I have setup both PowerDNS and bind9 for this purpose and I execute both bind9 and powerdns
monitor. All seems work perfectly! There's an AXFR zone-transfer to the slave (192.168.0.2) and the Resource Record's file was created. However, there's a problem, for example, when I add a RR on master and increment the serial for the slave update.

1) Initial situations
------+-------------------+-------.-+--------------+-----------+-----------------+---------+
| id   | name                | master | last_check   | type        | notified_serial | account |
+----+-------------------+---------+--------------+-----------+-----------------+---------+
|  6   | torvergata.local | NULL    |       NULL    | MASTER  |               0     | NULL    |
+----+-------------------+---------+--------------+-----------+-----------------+---------+

2) Update the serial : update domains set notified_serial=1 where id=6;

------+-------------------+-------.-+--------------+-----------+-----------------+---------+

| id   | name                | master | last_check   | type        | notified_serial | account |

+----+-------------------+---------+--------------+-----------+-----------------+---------+

|  6   | torvergata.local | NULL    |       NULL    | MASTER  |               1     | NULL    |

+----+-------------------+---------+--------------+-----------+-----------------+---------+

This is the pdns monitor's output:

Jan 25 07:00:23 Queued notification of domain 'torvergata.local' to 192.168.0.1
Jan 25 07:00:23 Queued notification of domain 'torvergata.local' to 192.168.0.2
Jan 25 07:00:24 Received NOTIFY for torvergata.local from 192.168.0.1 but slave support is disabled in the configuration
Jan 25 07:00:25 Removed from notification list: 'torvergata.local' to 192.168.0.2 (was acknowledged)
Jan 25 07:00:25 Received unsuccesful notification report for 'torvergata.local' from 192.168.0.1, rcode: 4
Jan 25 07:00:25 Removed from notification list: 'torvergata.local' to 192.168.0.1
Jan 25 07:00:27 No master domains need notifications

Reading the output I understand that master notify itself the change of zone, ans for me is normal that "slave support is disabled" beacause that server is master.

Both pc where both DNSserver are installed
use linux debian, and powerDNS's version is
2.9.21-4.

This is my powerdns' configuration file (pdns.conf):

gmysql-dbname=pdnstest
gmysql-host=127.0.0.1
gmysql-socket=/var/lib/mysql/mysql.sock
gmysql-password=XXX
gmysql-user=XXX
allow-axfr-ips=192.168.0.2
allow-recursion=127.0.0.1
config-dir=/etc/powerdns
daemon=yes
disable-axfr=no
disable-tcp=no
guardian=yes
launch=gmysql
lazy-recursion=yes
local-address=192.168.0.1
local-port=53
master=yes
module-dir=/usr/lib/powerdns
setgid=pdns
setuid=pdns
socket-dir=/var/run
version-string=powerdns
include=/etc/powerdns/pdns.d

This is my bind9 configuration's file about my zone (named.conf.local)

zone "torvergata.local"{
        type slave;
        file "/var/named/torvergata.local";
        masters { 192.168.0.1; };
};

I hope someone can help me because for me it's very very important find a solution.
A.B.


_________________________________________________________________
Scarica GRATIS le tue emoticon preferite!
http://intrattenimento.it.msn.com/emoticon/