[BUG] Error with include in zone files between primary and master

[JsdBEnZ7Rt9orgOfa1Ep1e4n]

Replace everything between stars with current version of your facileManager and module installations:
fM Version : 4.8.0 - from git fm_DNS Version : 6.3.0

In raising this issue, I confirm the following (please check boxes, eg [X]):

• [X] I have read and understood the contributors guide.
• [X] I have checked that the bug-fix I am reporting can be replicated, or that the feature I am suggesting isn't already present.
• [X] I have checked that the issue I'm posting isn't already reported.
• [X] I have checked that the issue I'm posting isn't already solved and no duplicates exist in closed issues and opened issues
• [X] I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion.

---

(BUG | ISSUE) Expected Behavior: Create a new A record in a zone Apply update by cron The include files in zones.conf.XXX is updated Example

/etc/bind/zones/master/db.toto.lan.hosts

(BUG | ISSUE) Actual Behavior: Create a new A record in a zone Apply update by cron The zone file in the folder primary is update. Example

/etc/bind/zones/primary/db.toto.lan.hosts

but the zones.conf.XXX include

/etc/bind/zones/master/db.toto.lan.hosts

I need to force Build Config for have update in the right file in the folder master

I tried to remove all zone file and force Build Config but the zones.conf.xxx files always include master folder

(BUG | ISSUE) Steps to reproduce:

Update from 4.5.0 Create a A entry in an existing zone simply apply by cron

Thanks for support

[JsdBEnZ7Rt9orgOfa1Ep1e4n]

I another instance of facileManager, the zones.conf.XXX use the primary folder. For the previous error, it's seems to be my BUG, why when I rebuild zones.conf.XXX files they include master directory and not the primary directory

[WillyXJ]

Thanks for testing before fmDNS v6.3.0 got released. What version of bind are you using? Do you see the same behavior when previewing the server configuration?

[JsdBEnZ7Rt9orgOfa1Ep1e4n]

I had the issue with the 4.7.0 (thats why i'm testing new release :))

I see the same issue in the preview configuration.

I have 4 servers managed with this release

3 server with release : 9.11.5-P4-5.1+deb10u11-Debian (Extended Support Version) 1 server with release : 9.16.50-Debian (Extended Support Version)

Only the server in 9.11 have the issue. It's OK in 9.16, the configuration include in zones.conf.XXX use primary directory

The only difference seems with the 9.16 server the Secondary zone directory is specify

[WillyXJ]

9.16.50 does not have a problem because it supports the updated nomenclature (primary/secondary). Bind 9.16.12 and earlier do not support the updated nomenclature. The bug in the fmDNS code is found and will be resolved in the next release.

[JsdBEnZ7Rt9orgOfa1Ep1e4n]

Thanks for fix Test done, it's OK for me thanks