Description Arvid Requate 2021-01-18 14:45:59 CET

Created attachment 10598 [details]
ip6.arpa.patch

Currently, the S4-Connector doesn't recognize IPv6-Zones when reading from Samba/AD:
==============================================================================
13.01.2021 17:28:53.383 LDAP        (PROCESS): sync from ucs: [           dns] [       add] DC=7.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0,dc=2.0.0.c.d.0.0.0.8.3.6.0.1.0.0
.2.ip6.arpa,cn=microsoftdns,dc=domaindnszones,DC=foo,DC=bar
13.01.2021 17:28:53.414 LDAP        (PROCESS): sync from ucs: [           dns] [    modify] dc=@,dc=2.0.0.c.d.0.0.0.8.3.6.0.1.0.0.2.ip6.arpa,cn=microsoftdns,dc
=domaindnszones,DC=foo,DC=bar
13.01.2021 17:28:54.535 LDAP        (PROCESS): sync to ucs:   [           dns] [
    modify] u'relativedomainname=7.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0,zonename=2.0.0.c.d.0.0.0.8.3.6.0.1.0.0.2.ip6.arpa,cn=dns,dc=foo,dc=bar'
13.01.2021 17:28:54.564 LDAP        (PROCESS): sync to ucs:   [           dns] [    modify] u'zonename=2.0.0.c.d.0.0.0.8.3.6.0.1.0.0.2.ip6.arpa,cn=dns,dc=foo,dc=bar'
13.01.21 17:28:54.566  ADMIN       ( ERROR   ) : object zoneName=2.0.0.c.d.0.0.0.8.3.6.0.1.0.0.2.ip6.arpa,cn=dns,dc=foo,dc=bar is not recognized as dns/forward_zone. Ignoring
for now. Please report!
==============================================================================

The attached may lead into the right direction to fix this.