SOA Serial no incrementing after records being added (A or CNAME).

[aredan]

I just installed facileManager and enable the DNS module, installed the client on 2 Debian servers. all this is for my internal network so no request from outside.

setup a test zone and build config for the 2 servers, after a few changes I noticed that the reload is always present and the Serial number (2016050300) is not being updated after a new A or CNAME record is added.

Downloaded the full package so I think that all the software is 2.2+

[WillyXJ]

So far I'm not able to reproduce this issue (tested with regular zones, clones, and templates). After you've built the server config for your DNS servers, added a record to a (built) zone, are you reloading the zone? The SOA serial numbers don't increment unless you reload the zone _*_and *__there are no reload errors. If you are reloading, are there any reload errors reported?

[aredan]

No errors after hitting _reload_icon in the Zones->forward.

I created the zone today and the Serial is always 2015050300.

The only strange this is that after hitting the reload icon, the message only says "zone Reload Results" and the OK button.

[aredan]

"I created the zone today and the Serial is always 2015050300." and added records just to force the Serial to increment.

The new records are in the server /zones/master/db.antigua.pw but the Serial is the same as the first build.

[WillyXJ]

This output looks like the reload is not actually occurring on your clients. There are a few things to check:

1. During your zone reload, what does /var/log/fm.log show on your DNS servers?
2. Can you please ensure Settings -> General -> Show Errors is enabled. Once enabled, see if there are any PHP errors displayed during the reload.
3. What update method are you using with your DNS servers?
4. Try running the reload manually on your DNS servers with:

sudo php /usr/local/facileManager/fmDNS/client.php zones id=14 debug

[aredan]

1. 
2. Yes "Show Errors" is enable. I cant see any errors.
3. HTTP.
4. 

In this image you can see that the Serial change from 00 -> 01 this was triggered by me applying a SOA template, the SOA Template have the following values:

This is my dashboard right now"

Right now I'm installing on another VM at work so I can see if this is replicated here.

[WillyXJ]

Thank you for this information. I've been able to reproduce it using the HTTP update method. A fix should come soon.

[WillyXJ]

You can manually apply the change to your DNS servers (client app) from 35d196a or wait until the next release.

[aredan]

I manually apply the change in my two nameserver.

First, I failed to mention that when I did a change in the Forward zone (adding a A record) the Serial didn't increase locally, I mean, when I click "Preview Config" the Serial still the same.

• Fix applied.

*Reload clicked.

*Serial still the same when Preview Config in the Zones->Forward.

*fm.log errors.

*If do a rebuild config to both servers.

[WillyXJ]

The serial number does not increment until after a successful reload on all servers configured to host the zone. In your case, it looks like it failed on odin.aanetworks.org and because of this failure the serial number did not increment.

You can verify the serial number increment by disabling odin.aanetworks.org in the Config -> Servers page, add/modify a record, and reload the zone.

Why odin.aanetworks.org is throwing an error on the reload is a separate issue. Is that zone configured to be hosted on "All Servers", a server group, or individual servers? I'm wondering if you've hit another bug as that error, in theory, should never appear when using the web interface. It might be easier to send me the output of the following database query:

SELECT `domain_name`,`domain_name_servers` FROM `fm_dns_domains` WHERE `domain_id`=6;

[aredan]

odin is set at the Zone template level. As you describe, if I remove odin the reload is send and the Serial is update everywhere.

This is the output of the SQL query.

I remove odin from my configuration for the the moment, I will try to add a 3er server that was running all my zones to see if the same error appear.

[aredan]

Removed the server, delete de config.inc.php and reinstalled the client the error keeps showing.
Something weird is that I made a group with leela and odin.

created a brand new zone for testing and configured that zone to used the group insted of individual servers and the error goes away, everything works as expected.

[WillyXJ]

Thank you for the additional information and your patience. I've confirmed this bug when individual servers are selected to serve the zone.

[WillyXJ]

Fix has been submitted. Either wait for the next release or manually apply the change to class_buildconf.php from ee6deab

[WillyXJ]

v2.2.2 has been released with both of these fixes.