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

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

Closed
aredan opened this Issue May 3, 2016 · 14 comments

Comments

Projects
None yet
2 participants
@aredan

aredan commented May 3, 2016

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

This comment has been minimized.

Owner

WillyXJ commented May 3, 2016

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?

@WillyXJ WillyXJ added the fmDNS label May 3, 2016

@aredan

This comment has been minimized.

aredan commented May 3, 2016

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

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

2016-05-03 11_34_48-forward zones facilemanager
2016-05-03 11_35_08-forward zones facilemanager
2016-05-03 11_35_46-remote desktop manager free jumper

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

@aredan

This comment has been minimized.

aredan commented May 3, 2016

"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 comment has been minimized.

Owner

WillyXJ commented May 3, 2016

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

This comment has been minimized.

aredan commented May 3, 2016

  1. 2016-05-03 12_16_37-remote desktop manager free jumper
  2. Yes "Show Errors" is enable. I cant see any errors.
  3. HTTP.
  4. 2016-05-03 13_54_26-remote desktop manager free jumper

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:

2016-05-03 13_56_58-soa templates facilemanager

This is my dashboard right now"

2016-05-03 13_57_47-dashboard facilemanager

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

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented May 3, 2016

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

@WillyXJ WillyXJ added this to the 2.x bug fixes milestone May 3, 2016

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented May 3, 2016

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

@aredan

This comment has been minimized.

aredan commented May 3, 2016

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.

2016-05-03 15_11_49-server config preview facilemanager

  • Fix applied.

2016-05-03 15_14_27-greenshot capture form

*Reload clicked.

2016-05-03 15_15_07-server config preview facilemanager
*Serial still the same when Preview Config in the Zones->Forward.

2016-05-03 15_16_37-remote desktop manager free jumper
*fm.log errors.

2016-05-03 15_24_15-name servers facilemanager
2016-05-03 15_23_45-remote desktop manager free jumper

*If do a rebuild config to both servers.

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented May 3, 2016

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

This comment has been minimized.

aredan commented May 4, 2016

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.
2016-05-03 20_19_38-cortana

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

This comment has been minimized.

aredan commented May 4, 2016

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.

2016-05-03 21_59_24-name servers facilemanager

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.

2016-05-03 22_01_15-reverse zones facilemanager

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented May 4, 2016

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

WillyXJ added a commit that referenced this issue May 4, 2016

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented May 4, 2016

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

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented May 6, 2016

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

@WillyXJ WillyXJ closed this May 6, 2016

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