bind-dyndb-ldap

#119 Serving reverse zones for private ranges requires manual change in named.conf
Closed: Fixed Opened by pspacek.

Closed: Fixed
Reopen Issue

From BIND version 9.9, the "automatic empty zones" defined in RFC 6303 are automatically enabled.

This prevents bind-dyndb-ldap from loading reverse zones listed in RFC 6303 section 4.

Workaround

Add line like

disable-empty-zone "8.b.d.0.1.0.0.2.ip6.arpa.";

to /etc/named.conf for each 'local' reverse zone in LDAP.

Further reading

  • https://kb.isc.org/article/AA-00800 (free registration required)

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=962815

Steps to reproduce:

  • Add e.g. reverse zone 8.b.d.0.1.0.0.2.ip6.arpa. to IPA DNS
  • Add arbitrary record to the reverse zone
  • Try to dig the record or read logs from named: Zone is not loaded and records are not available to clients, because default empty zones are loaded before zones from IPA DNS

Fixed by c9cdbe34b0d9a514d2b95a295d239ce0b2a0386f

Fixed by 3df30edeae3e1025c899338b554460aa9f0c742e

Fixed by 96f795180d182bcc008159e5ce0102af9fc8324f

Metadata Update from @pspacek:
- Issue assigned to pspacek
- Issue set to the milestone: Fedora 19

Log in to comment on this ticket.

Metadata
None
None
None
Normal
defect
ldap driver
3.1
nihsyndrome
https://bugzilla.redhat.com/show_bug.cgi?id=962815
Powered by Pagure 1.0.0
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.