Ticket #504 (closed defect: duplicate)
Double AXFR transfer off a record
| Reported by: | anon | Owned by: | somebody |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | auth | Version: | 3.1 |
| Severity: | minor | Keywords: | AXFR |
| Cc: | henrypa@… |
Description
When I do a 'pdns_control notify <domain>' once, the master seems to send the AXFR twice.
This is what I see in the slave logs:
AXFR started for 'vuurwerk.nl', transaction started AXFR started for 'vuurwerk.nl', transaction started AXFR done for 'vuurwerk.nl', zone committed with serial number 2012050901 AXFR done for 'vuurwerk.nl', zone committed with serial number 2012050901
Is this 'by design' or a bug? and/or is this generating extra overhead for AXFR requests?
For the record: This is a sync from tinydns backend master to mysql backend slave.
Regards, Henry Paulissen
Change History
Note: See
TracTickets for help on using
tickets.