[Pdns-users] pdns_control appears with wrong IP on slave - supermaster setup

[Konstantin Kletschke]

Hello,

yesterday I reviewed my config and did one significant change, there was 
one error done by me.

As (not) said, the server/master has IPs 81.3.11.18, 81.3.11.19 and 
81.3.11.20 available, but has

local-address=81.3.11.19 in its config.

Then on the slave, the nameserver FQDN defining the slave was wrong, now 
it looks like this:

+------------+------------------+---------+
| ip         | nameserver       | account |
+------------+------------------+---------+
| 81.3.11.19 | ns2.ku-gbr.de.de | admin   |
+------------+------------------+---------+

Still I am testing on mig19.de and still face two problems:

If i enter command

"pdns_control notify mig19.de"

on the master the slave says

"Received NOTIFY for mig19.de from 81.3.11.18 which is not a master".

Of course 81.3.11.18 is not the master, 81.3.11.19 is. How comes that 
notify reaches the slave from the wrong IP?
Can this be caused by firewall settings on the slave (master has none)? 
TCP and UDP Port 53 is opened in both directions.

Additionally I don't see the cause of this:

When I try to fetch on the slave with

"pdns_control retrieve mig19.de"

the slave says

"Domain 'mig19.de' is not a slave domain (or has no master defined)"

This is the records output for mig19.de on master and slave (In SOA 
record I changed ns2.ku-gbr.de to ns1.ku-gbr.de):

id, domain_id, name, type, content,ttl, prio, change_date, disabled, 
ordername, auth

+-----+----+----------+-----+-------------------------------------+--------+-------+------+---+-+---+
| 333 | 32 | mig19.de | SOA | ns2.ku-gbr.de. hostmaster.mig19.de. |      
   |       |      |   | |   |
|     |    |          |     | 1449513605 16384 2048 1048576 2560  | 
259200 |     0 | NULL | 0 | | 1 |
| 334 | 32 | mig19.de | A   | 1.1.1.20                            |  
86400 |     0 | NULL | 0 | | 1 |
| 336 | 32 | mig19.de | MX  | mail.mig19.de                       |  
86400 | 86400 | NULL | 0 | | 1 |
| 337 | 32 | mig19.de | NS  | ns1.ku-gbr.de                       | 
259200 |     0 | NULL | 0 | | 1 |
| 338 | 32 | mig19.de | NS  | ns2.ku-gbr.de                       | 
259200 |     0 | NULL | 0 | | 1 |
+-----+----+-------------+-----+----------------------------------+--------+-------+------+---+-+---+

Has this something to do with the type field for mig19.de in table 
domains? Is this relevant in supermaster setup? Actually I tried NATIVE, 
SLAVE and SUPERSLAVE, all the same...

Kind Regards
Konstantin