...

1. Select any tab in Grid Manager, and then click IDN Converter from the Toolbar.
2. In the IDN Converter wizard, complete the following:
   • Specify the domain name in the Unicode text box and click Convert to Punycode. The Punycode field displays the punycode representation of the domain name.
   • Specify the punycode representation of a domain name in the Punycode field and click Convert to Unicode.
     The Unicode field displays the domain name in its original character set.

Note: You can use special characters in the Unicode and Punycode fields.

• Click Clear to clear the entries. Note that when you click Clear for a specific conversion, the appliance clears only the error message that corresponds to that conversion.

1. Click Close.

Anchor
IDN Supported Fields IDN Supported Fields

Anchor
bookmark210 bookmark210

IDN Supported Fields

The NIOS appliance supports IDNs in all domain name fields. For information, see IDN Support For DNS Zones on page 872. You can enter non-English characters in the domain name fields through Grid Manager and the Infoblox API. The NIOS appliance does not support IDNs for data that is configurable through the Infoblox CLI commands. You can use the punycode representation to configure data through the CLI commands.
The appliance supports IDNs in the following:

• • You can use UTF-8 characters when defining your own hostname checking policy. For information, see

Specifying Hostname Policies .

...

The appliance has the following IDN support limitations:

• • F5® load balancers does not support IDNs. The NIOS appliance does not encode punycode to IDNs for F5 load balancer related objects. Only the punycode representation is available.
  • Multi-Grid configuration does not support IDNs.
  • The Infoblox CLI does not support IDNs.
  • If a resource record containing an IDN is added to the Infoblox Grid through DDNS updates, the domain name field displays the record name in UTF-8 encoded format. For more information, see Managing Resource Records .
  • The following FQDNs does not support IDNs:
    • FQDN of an external DNS Server (direct or via name server group)
    • FQDN of a DNS root server
    • FQDN of a Microsoft server
    • FQDN of an Infoblox Grid Member
    • FQDN of an external authentication source (Active Directory, LDAP, OCSP, RADIUS, TACACS+)
    • FQDN of an NTP server
    • FQDN of a HSM SafeNet Module
    • FQDN of an email relay server
    • FQDN of a vSphere/ESX server
    • FQDN of a Kerberos Key Distribution Center

Using IDNs for Unsupported Objects

...