Hi Martin,
I changed SOA to mention ns1.ku-gbr.de as I like it better to have
ns1.ku-gbr.de as the main ns server anyway.
But into supermasters there has to go the IP of the master (ip), the
FQDN of the salve (nameserver) and a random string into (account), is
that correct?
Am 2015-12-10 17:57, schrieb Martin:
Have you tried specifying NS1's FQDN instead of NS2's in the
supermaster table, and having NS1 in the SOA record instead of NS2?
Slave setup (entries in records identical to master):
mysql> select * from records where name='mig19.de';
+-----+-----------+----------+------+------------------------------------+--------+-------+-------------+----------+-----------+------+
| id | domain_id | name | type | content
| ttl | prio | change_date | disabled | ordername | auth |
+-----+-----------+----------+------+------------------------------------+--------+-------+-------------+----------+-----------+------+
| 334 | 30 | mig19.de | A | 81.3.11.20
| 86400 | 0 | NULL | 0 | | 1 |
| 336 | 30 | mig19.de | MX | mail.ku-gbr.de
| 86400 | 86400 | NULL | 0 | | 1 |
| 337 | 30 | mig19.de | NS | ns1.ku-gbr.de
| 259200 | 0 | NULL | 0 | | 1 |
| 338 | 30 | mig19.de | NS | ns2.ku-gbr.de
| 259200 | 0 | NULL | 0 | | 1 |
| 333 | 30 | mig19.de | SOA | ns1.ku-gbr.de.
| | | | | | |
| | | | | hostmaster.mig19.de.
| | | | | | |
| | | | | 1449513605 16384 2048 1048576 2560
| 259200 | 0 | NULL | 0 | | 1 |
+-----+-----------+----------+------+------------------------------------+--------+-------+-------------+----------+-----------+------+
5 rows in set (0.00 sec)
mysql> select * from domains where name='mig19.de';
+----+----------+--------+------------+--------+-----------------+---------+
| id | name | master | last_check | type | notified_serial |
account |
+----+----------+--------+------------+--------+-----------------+---------+
| 30 | mig19.de | NULL | NULL | SUPERM | NULL | NULL
|
+----+----------+--------+------------+--------+-----------------+---------+
1 row in set (0.00 sec)
mysql> select * from supermasters;
+------------+---------------+---------+
| ip | nameserver | account |
+------------+---------------+---------+
| 81.3.11.19 | ns1.ku-gbr.de | admin |
+------------+---------------+---------+
1 row in set (0.00 sec)
When I enter command on the master:
"pdns_control notify mig19.de"
In the master's syslog this - still - appears:
Dec 11 07:24:50 kermit pdns[24806]: Received NOTIFY for mig19.de from
81.3.11.19 but slave support is disabled in the configuration
which is okay, since master gets notified also and does refuse to handle
as a slave. In the slave's syslog I see this:
Dec 11 07:25:00 v22015082965927173 pdns[6829]: Received NOTIFY for
mig19.de from 81.3.11.18 which is not a master
Dec 11 07:25:00 v22015082965927173 pdns_server[6810]: Dec 11 07:25:00
Received NOTIFY for mig19.de from 81.3.11.18 which is not a master
Note the difference on master and slave: "NOTIFY [...] from 81.3.11.19"
and "NOTIFY [...] from 81.3.11.18"
When I enter command to retrieve on the slave I get:
root@v22015082965927173:~# pdns_control retrieve mig19.de
Domain 'mig19.de' is not a slave domain (or has no master defined)
This may be related to the wrong entry "SUPERM" for type in domains
table on slave I actually see. Might happened while trying NULL, NATIVE,
SLAVE and SUPERSLAVE but ended putting SUPERM(ASTER) into by accident. I
tried many permutations already and messed up.
Kind Regards
Konstantin Kletschke
_______________________________________________
Pdns-users mailing list
[email protected]
http://mailman.powerdns.com/mailman/listinfo/pdns-users
