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 Seres