[Pdns-users] Question on IPv6 with ldap backend

[Nikolaos Milas]

  Hi,

I would like some clarifications on the configuration of IPv6 zones on 
LDAP backend.

I have a master pdns/ldap (tree mode) server hosting "example.com" and 
its reverse zone: 10.10.10.in-addr.arpa.

The DNS server shall support IPv6.

Questions:

   1. For forward lookups, should I create a new zone v6.example.com
      (with its own SOA) to place AAAA records etc or should I place
      AAAA records in the existing example.com zone branch (mixed with
      ipv4 A records)? Likewise, ipv6 MX records should be defined
      separately in v6.example.com or the existence of AAAA records for
      the existing ipv4 MX records is sufficient?
   2. For reverse lookups, where I need to configure a /48 zone for
      assigned ipv6 addresses:
         1. I should create a separate zone arpa.ip6 /48 with its own
            SOA record, like arpa.ip6.f.e.8.0.0.1.0.0.0.1.0.0 (already
            14 levels deep - below ou=dns)?
         2. For a record with an ipv6 address like:
            fe80:100:100:1::1/48, I should create ldap branches - 34 (!)
            levels deep - as below?

        arpa.ip6.f.e.8.0.0.1.0.0.0.1.0.0.0.0.0.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1

Clearly, if I should make such branches for reverse lookups, it is 
beyond control. I should inevitably migrate to ldap "simple" mode. Is 
there a script to convert from ldif in tree mode to ldif simple mode, so 
that migration is smooth? Or I should take a standard zone format (e.g. 
as produced from an AXFR) and use this with zone2ldap?

Please advise, because I'm confused.

Thanks,
Nick