Upgrdading all pdns authoritative servers to 4.2.2 fixed the issue.
Still, I think this is a bug or undocumented feature, because the pdns
settings were same, the SQL database was synced and still pdns
authoritative 4.1.13 and 4.4.2.2 replied different serials.
With best regards,
--
Cristian
Hi Christian,
On 5/15/20 4:03 PM, Cristian Seres via Pdns-users wrote:
> they seem to match:
> [...]
I did some digging and found out the behaviour for INCEPTION-INCREMENT
changed between 4.1 and 4.2 (in 4.2.0-alpha1) in commit f613d242[1] in
PR #4547[3]. As we'd increase the SOA serial by 2
Pieter Lexis via Pdns-users wrote:
Can you check the default-soa-edit* settings between the different
instances? A difference might explain this, as the SOA serials in the
database and (unrelated) metadata match.
Hi Pieter,
they seem to match:
[ns1 ~]$ sudo pdns_control current-config|grep
Hi Christian,
On 5/14/20 3:20 PM, Cristian Seres via Pdns-users wrote:
> one of three authoritative name servers (ns3) which uses authoritative
> version 4.2.2 gives older serial number than the other two which use
> version 4.1.13.
Can you check the default-soa-edit* settings between the
Otto Moerbeek wrote:
On Thu, May 14, 2020 at 04:20:46PM +0300, Cristian Seres via Pdns-users wrote:
AFAIK, if you are using native replication, the type of your zone
should be native and not master.
Sorry, my mistake in the email, this test domain is actually native:
MariaDB [powerdns]>
On Thu, May 14, 2020 at 04:20:46PM +0300, Cristian Seres via Pdns-users wrote:
> Hi,
>
> one of three authoritative name servers (ns3) which uses authoritative
> version 4.2.2 gives older serial number than the other two which use version
> 4.1.13.
>
> MySQL sync is working properly and as far
Hi,
one of three authoritative name servers (ns3) which uses authoritative
version 4.2.2 gives older serial number than the other two which use
version 4.1.13.
MySQL sync is working properly and as far as I can see, databases are
identical. Also executing pdns-util increase-serial on the
