On 26/07/2018 11:15, Frank Altpeter wrote:
The value returned from the real primary:
freddy@hades ~ % dig +short +noshort floppysheep.com
<http://floppysheep.com> soa @koef.zs64.net <http://koef.zs64.net>
floppysheep.com <http://floppysheep.com>.432000INSOAkoef.zs64.net
<http://koef.zs64.net>. hostmaster.zs64.net
<http://hostmaster.zs64.net>. 2018072400 86400 3600 3888000 300
The value returned from the hidden primary:
freddy@hades ~ % dig +short +noshort floppysheep.com
<http://floppysheep.com> soa @p-dns.irz42.net <http://p-dns.irz42.net>
floppysheep.com <http://floppysheep.com>.432000INSOAkoef.zs64.net
<http://koef.zs64.net>. hostmaster.zs64.net
<http://hostmaster.zs64.net>. 2018072601 86400 3600 3888000 300
The value returned from the second slave (directly syncing from the
real primary):
freddy@hades ~ % dig +short +noshort floppysheep.com
<http://floppysheep.com> soa @s-dns.irz42.net <http://s-dns.irz42.net>
floppysheep.com <http://floppysheep.com>.432000INSOAkoef.zs64.net
<http://koef.zs64.net>. hostmaster.zs64.net
<http://hostmaster.zs64.net>. 2018072400 86400 3600 3888000 300
As you see, both the master and the second slave have 2018072400 as
serial, but the hidden primary has the serial 2018072601.
The problem is, I have no clue where this serial is coming from. The
domain is configured via bind backend so the serial has to come from
the zonefile itself, but it isn't:
p-dns:~ # grep SOA /var/named/slave/floppysheep.com
<http://floppysheep.com>
@432000SOAkoef.zs64.net <http://koef.zs64.net>. hostmaster.zs64.net
<http://hostmaster.zs64.net>. 2018072400 86400 3600 3888000 300
Which server is that file on? The hidden primary, real primary, or slave?
Anyway, if I do a query now, it seems to have updated:
$ dig +trace floppysheep.com. soa
...
floppysheep.com. 172800 IN NS p-dns.irz42.net.
floppysheep.com. 172800 IN NS s-dns.irz42.net.
;; Received 114 bytes from 192.5.6.30#53(192.5.6.30) in 191 ms
floppysheep.com. 432000 IN SOA koef.zs64.net.
hostmaster.zs64.net. 2018072601 86400 3600 3888000 300
;; Received 93 bytes from
2a00:14b0:4200:8600::30#53(2a00:14b0:4200:8600::30) in 35 ms
(That IPv6 address shows the query went to p-dns.irz42.net)
It could just be that you don't have notifications configured properly,
so the slaves (including "real primary" which is really a slave) only
update periodically. You have a refresh interval of 86400 seconds set,
so it could take that long for the updates to propagate if notifications
aren't working.
Regards,
Brian.
_______________________________________________
Pdns-users mailing list
[email protected]
https://mailman.powerdns.com/mailman/listinfo/pdns-users