New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Serial numbers not updated on cloned zones #330

karlism opened this Issue Jul 14, 2016 · 2 comments


None yet
2 participants

karlism commented Jul 14, 2016


There is an issue with serial numbers and zone reloads when using cloned zone feature. To reproduce it do the following:

  1. create a new zone (with proper SOA record and NS records so that facileManager deploys it to server);
  2. create a clone of that zone (I'm using same name of the zone but different view);
  3. deploy these zones to server configuration and note/remember serial numbers of both zones (master and clone);
  4. add new A record in master zone (that was created in first step), do not reload server configuration yet:
    3.1) verify that both zones (created in step 1 and step 2) now contain this new A record in web interface;
    3.2) reload this zone;
  5. if you check serial numbers on DNS servers (or from zone preview page), you'll notice that serial number has been updated only on master zone (created in step 1), but not on its clone (created in step 2).

This comment has been minimized.


WillyXJ commented Jul 18, 2016

Thanks for the report - I have confirmed this bug using your provided steps.


This comment has been minimized.


WillyXJ commented Jul 22, 2016

This has been fixed in v2.2.4.

@WillyXJ WillyXJ closed this Jul 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment