For many years now, IDN has been a natural part of most domaintypes.
For Whmcs the integration of IDN has only started, causing many problems for clients that actually sell IDN related products every day.
The latest response from WHMCS, after we had faced a problem with IDN registration of a simple .COM domain name, was:
"Regrettably IDN are not supported by registrar modules in WHMCS at this
time. Each different registrar has implemented IDNs in a different way
and we need to find a way that is compatible with all of them, which is
proving quite a challenge.
However this is a problem we are always looking for a solution and hope to have implemented at some point in the future."
That response is simply not good enough as we had an almost similar answer 3-4 years ago...
Presently an IDN order through Whmcs even causes misregistrations where Whmcs interprets the punicode wrong and then simply registers a completely different name than wanted and not even a punicode name, leaving you with registred domainnames that are to no use at all...
The least Whmcs could do was to throw such an order out to manual registration instead of just registrering some completely different names than the actually ordered..
Give this the HIGHEST priority - Whmcs clients are having losses and problems because of this BUG in Whmcs.
IDN support for Chinese Traditional words
there are some words in Chinese Traditional will result in errors in domain registration. only solution right now for us is write into MySQL directly.problem words are the followingsç«¥è£æ‰¹ç™¼.å°ç£ BADå°ä¸é€¢ç”²æ°‘å®¿ç¶².å°ç£ GOODproblem words are the followingsç£,è£,è£¡xn--or2aa.comxn--or2aa.twxn-sr2aa.twxn-sr2aa.comand our client has the following domain registrar registered with other registrarXN--1NR70AM32J.COMxn--kjv538e.xn--kpry57dI'm sure there are more.see my demo video on youtube.http://www.youtube.com/watch?v=DVekxTfRLF0
better idn registration
currently there is some bugs that i have found that our client wasn't able to transfer their domain name over to us.see the youtube demo videohttps://www.youtube.com/watch?v=DVekxTfRLF0ç«¥è£æ‰¹ç™¼.com BADç«¥è£æ‰¹ç™¼.å°ç£ BADå°ä¸é€¢ç”²æ°‘å®¿ç¶².å°ç£ GOODproblem words are the followingsç£,è£,è£¡,æ£any domain contain any of those 4 words will fail.e.g.ç£ç£.comè£è£.comè£¡è£¡.comæ£æ£.comor you can add any random number in front or between or after those words.e.g.122121ç£ç£.comç£ç£12212121.com-there could be more problem words, but these are the few I know.
eNom Registrar IDN Support
We would like to be able to offer IDN/UTF-8 domains to our customers. This requires the eNom module to be updated to convert UTF-8 domains to punycode before making the register request.
IDN is not working with RRPproxy or a lots of other Registrars. Letters will be renamed from ü to u or ä to the letter 'a' instead of converting to Punnycode. WHMCS registers and managed the wrong domain.As a example:Customer orders müller.com. WHMCS registered muller.com instead of xn--mller-kva.com same issue happens on transfer, also domainmanagement is not working except the customer orders the domain with Punnycode.