#8287 named not starting after #8079, ipa-ext.conf breaks bind
Closed: fixed 3 years ago by cheimes. Opened 3 years ago by carbenium.

Issue

With the patch described in #8079 applied and a /etc/named/ipa-ext.conf file containing an options section e.g.

options {
  allow-recursion { any; };
};

named fails to start with following error message:
/etc/named/ipa-ext.conf:17: 'options' redefined near 'options'

Version/Release/Distribution

4.8.6 Fedora 31


I'm able to confirm the issue. named.conf cannot have multiple options blocks. The patch 6c27104 is broken by design. I guess the documented override in ipa-ext.conf was not tested.

Proposed fix: Define two override files, one for options and one for general config stanzas like ACLs.

Metadata Update from @cheimes:
- Issue priority set to: important
- Issue set to the milestone: FreeIPA 4.8.7

3 years ago

Just an idea (maybe a bad one):

Since we have now the possibility to include custom configuration from a file which is not managed by FreeIPA, we could treat the whole named.conf file as a template and recreate it during upgrades. This would make the upgrade code in ipaserver/install/bindinstance.py and ipaserver/install/server/upgarde.py a whole lot simpler.

master:

  • a5cbdb5 Split named custom config to allow changes in options stanza
  • 6e5d40e Include named config files in backup

ipa-4-8:

  • 539d469 Split named custom config to allow changes in options stanza
  • 782ee11 Include named config files in backup

Metadata Update from @abbra:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Metadata Update from @cheimes:
- Issue status updated to: Open (was: Closed)

3 years ago

Metadata Update from @cheimes:
- Issue close_status updated to: fixed
- Issue set to the milestone: None (was: FreeIPA 4.8.7)
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata