#134 Child DNS zone is corrupted if parent zone is hosted on the same server
Closed: Fixed None Opened 9 years ago by pspacek.

Problem

Child DNS zone is corrupted and cannot be loaded if the parent zone is hosted on the same server.

Steps to Reproduce

  • Run following three tests from FreeIPA test suite: ipatests/test_xmlrpc/test_dns_plugin.py

    dnszone_add: Create reverse zone u'1.168.192.in-addr.arpa.'
    dnszone_add: Create classless reverse zone u'128/25.1.168.192.in-addr.arpa.'
    dnsrecord_add: Add NS record to u'128/25' in revzone u'1.168.192.in-addr.arpa.'

  • More specifically:

    • Add reverse zone 1.168.192.in-addr.arpa.
    • Add reverse zone 128/25.1.168.192.in-addr.arpa.
    • Add delegation (NS record) 128/25 to the zone 1.168.192.in-addr.arpa.

Named log will show following error:

zone 128/25.1.168.192.in-addr.arpa/IN: starting load
zone 128/25.1.168.192.in-addr.arpa/IN: number of nodes in database: 1
zone 128/25.1.168.192.in-addr.arpa/IN: loaded; checking validity
zone 128/25.1.168.192.in-addr.arpa/IN: has 0 SOA records
zone 128/25.1.168.192.in-addr.arpa/IN: not loaded due to errors.
zone 128/25.1.168.192.in-addr.arpa/IN: unable to load zone: bad zone

Debug log level 7+ shows the cause:

add 128/25.1.168.192.in-addr.arpa. 86400 IN SOA ns2.zone3.test. root.zone3.test. 1396368717 3600 900 1209600 3600
add 128/25.1.168.192.in-addr.arpa. 86400 IN NS  ns2.zone3.test.
zone 128/25.1.168.192.in-addr.arpa/IN: writing new zone serial 1396368717 to LDAP
writing to 'idnsname=128/25.1.168.192.in-addr.arpa.,cn=dns,dc=ipa,dc=example': modifying(replace)
syncrepl_update: updating name in rbtdb, dn: 'idnsname=128/25,idnsname=1.168.192.in-addr.arpa.,cn=dns,dc=ipa,dc=example'
del 128/25.1.168.192.in-addr.arpa. 86400 IN SOA ns2.zone3.test. root.zone3.test. 1396368717 3600 900 1209600 3600

Update from LDAP object idnsname=128/25,idnsname=1.168.192.in-addr.arpa.,cn=dns,dc=ipa,dc=example incorrectly modifies child DNS zone idnsname=128/25.1.168.192.in-addr.arpa.,cn=dns,dc=ipa,dc=example.

Environment

Plugin version: 4.0+


Steps to reproduce clarified.

Already fixed downstream, no need to clone.

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

6 years ago

Login to comment on this ticket.

Metadata