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

Multiple views can not share the same cache file #367

Closed
wheelmanstudio opened this Issue Mar 19, 2017 · 4 comments

Comments

Projects
None yet
2 participants
@wheelmanstudio

wheelmanstudio commented Mar 19, 2017

After an upgrade to 9.10 my bind stopped with a message:
/etc/bind/zones/zones.conf.external:24: writeable file '/etc/bind/zones/slave/db.localhost.hosts': already in use: /etc/bind/zones/zones.conf.saima:29
It is because of two views sharing the same slave zone file. I will just leave it here: issue details

We need some new zone file generation mechanism for slaves.

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Mar 20, 2017

Thanks for the report. It should be simple enough to add the domain_id to the filename which is already done for master zones.

@WillyXJ WillyXJ added this to the 3.0 release milestone Mar 20, 2017

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Mar 20, 2017

What version of fmDNS are you using? I just tested with 2.2.6 and it already supports unique slave file names.

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Mar 31, 2017

Further test scenarios confirmed this bug. Initial tests were using split-view zones which did not reveal this bug.

fM Version : 2.3.3
fmDNS Version : 2.2.6

Expected Behavior:
A single zone in multiple views would have unique slave cache files.

Actual Behavior:
A single zone in multiple views share the same slave cache file thus generating a bind error:

Your named configuration contains one or more errors:/etc/named/zones/zones.conf.External:61: writeable file '/etc/named/zones/slave/db.test-domain.local.hosts': already in use: /etc/named/zones/zones.conf.Internal:78

Steps to reproduce:

  1. Create a server group with one master and at least one slave.
  2. Create two or more views
  3. Create a zone in "All Views"
  4. Build the config on all servers in the group
@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Apr 15, 2017

This is now fixed in the latest beta version and later.

@WillyXJ WillyXJ closed this Jun 23, 2017

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