Moving my tickets back to free-to-take pool.

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=1009670 (Fedora)

We should at least allow creating punycode names directly.
No need to translate from utf8 if we think it is too difficult, but preventying puny names is just ridiculous IMO.

Bumping up.

Petr, how does puny code works with Fedora 19 version of bind-dyndb-ldap and how does it work with future RTDB based bind-dyndb-ldap? Allowing punycode in FreeIPA validation functions is one thing, but support in bind-dyndb-ldap is another thing.

It should simply work, from bind-dyndb-ldap perspective it is normal ASCII string.

Related: #1845.

Adjusting time plan - 3.4 development was postponed as we focused on 3.3.x testing and stabilization.

Adjusting time plan - 3.4 development was postponed as we focused on 3.3.x testing and stabilization.

Only draft patch

This ticket is not complete yet, moving to next month milestone.

master:

• 47f473d Allows to sort non text entries
• 9c7b0ad DNSName type
• 64d8da2 DNSNameParam parameter
• 7625c02 dns_name_values capability added
• d0cf1f3 get_ancestors_primary_keys clone
• b9969c6 CLI conversion of DNSName type
• d0ce647 DNSName conversion in ipaldap
• e70f88c Modified has_output attributes
• b964d21 Modified dns related global functions
• a4d3d01 Modified records and zone parameters to use DNSNameParam
• 5b88b39 Modified record and zone class to support IDN
• dafd162 _domain_name_validatord moved from DNS to realmdomains
• 0827b95 move hostname validation from DNS to hosts
• ef71d88 DNS modified tests
• 7860c63 DNS new tests
• fa21899 PTR record target can be relative

Additional fix:

• 7bf30ae Fix indentation

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