On Aug 26, 2022, at 11:20 AM, Meir Kraushar via dns-operations <[email protected]> wrote: > Yes the problem is that browsers not aware of a TLD, in this case SAFARI > unaware of xn--4dbrk0ce, do not treat it as a domain. It won't resolve the > given name and go to the address. Instead, it will pass the value to the > search engine. This is bad. Most certainly not the desired behavior when > launching a new domain.
The problem is not that "browsers not aware of a TLD", it is that they are having a problem with the right-to-left conversion in that name. For example, using another ccTLD IDN such as xn--4gbrim works fine. Firefox works correctly when you enter the non-existent "nic.xn--4dbrk0ce", but Safari and Chrome fall back to search. All three work fine when entering the non-existent "nic.xn--4gbrim". --Paul Hoffman
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ dns-operations mailing list [email protected] https://lists.dns-oarc.net/mailman/listinfo/dns-operations
