bind-dyndb-ldap

#168 per-server forwarders in LDAP do not trigger warning messages as they should
Closed: Invalid Opened by pspacek.

Closed: Invalid
Reopen Issue

Problem

  • What does not work as expected?

Warnings about conflicting configuration between global forwarding and automatic empty zones are not printed when global forwarding is configured at server level.

Steps to Reproduce

  • Make sure you do not have any forwarding configured in /etc/named.conf
  • Configure per-server global forwarder: $ ipa dnsserver-mod <fqdn> --forwarder=192.0.2.1
  • Check named logs. They should contain warning about conflict between automatic empty zone and global forwarder.
  • The warning is not there :-)

Environment

  • Plugin version: master, to-be v11

  • dynamic-db section from configuration file /etc/named.conf:

contains option "server_id" which matches an server object in LDAP

The warning is displayed with BIND 9.11 and bind-dyndb-ldap 11.0.

Metadata Update from @tkrizek:
- Issue assigned to tkrizek
- Issue set to the milestone: 0.0 TRIAGE

Log in to comment on this ticket.

Metadata
None
None
None
Normal
defect
ldap driver
Powered by Pagure 1.0.0
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.