Task #25 — Wrong serial number matching for slave domains
Attached to Project — PDNS OpenDBX
Opened by Vladimir Linek (ViNiL) - Friday, 20 Nov 2009, 12:00pm
| Bug Report | Low | ||
| Backend / Core | Normal | ||
| Unconfirmed | 1.0 | ||
| No-one | Undecided | ||
| All |  |
||
|
We have two powerdns 2.9.22 with opendbx/sqlite3 here. Each of the server has two master domains and should have two slave domains from the other server, which is set as supermaster. We use the auto serial feature. One server is running gentoo, the other one is running debian. Both on amd64 platform. The master domains and the first slave domain works well. Here comes the issue: with the second slave domain, the serial id comparisons start to fail (see below) and one of the slave domain is dropped. See example log line (1st.domain has serial 51 on master, 2nd.domain has serial 49): Domain 2nd.domain more recent than master, our serial 102 > their serial 49 Note, that 2nd.domain's serial number is compared to 1st.domain's serial number, shift one bit to the left! (It's always this way). Can't there be any pointer/cast bug? |
|||
Comments (4) | Attachments (2) | Related Tasks (0/0) | Notifications (1) | Reminders (0) | History |
These tasks are related to this task
Other tasks that this task is related to