Comment 7 for bug 2060024
Revision history for this message
| Erik Olof Gunnar Andersson (eandersson) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Thanks for the update.
I don’t know the cause, but we made a significant change with how notifications are sent in this version of Designate. In the previous version it would notify on each change, and now we batch all changes and only notify every 5 second per zone. Depending on use patterns the upstream DNS server should see exponentially less notifies from designate and maybe that caused the behavior you were seeing, as previously it would be spamming your bind servers.