In DNS, the domain name has to be ASCII, so unicode characters in the domain name are converted to Punycode and prefixed with xn--. So really, blåhaj.com is really xn--blhaj-nra.com (put that in your browser and watch the name change).
I would imagine that most things would just work, but there would probably be some annoying bugs with different clients who aren't using libraries which support internationalized domain names, or aren't expecting them. It'd probably be a good thing to have an internationalized domain name for a popular instance, as that would be a good test case for servers and clients to support that standard.
I'm personally convinced limitations like this are why English is becoming such a dominant language, because the internet and most coding was all designed in English for English, without consideration for other languages. Other languages have to get tacked on with semi-complicated workarounds like this.
Never attribute to malice that which is adequately explained by stupidity.
All of this stuff is 50 years old and there's no way the people who put these systems in place could have ever predicted the Internet as it is today. Famously in 1973, there was a "map of the ARPA network", that's how few machines were "online" at the time.
It's really only in the past 10 years or so that security via TLS has been widely adopted by websites, and it's been over 20 years since IPv6 was announced and still is not entirely supported everywhere. There is so much inertia with the underlying infrastructure of the internet, even if there is a serious issue (like DNS cache poisoning ), systems will not be reworked and replaced, but hacks will be added to fix the issue of the day.
Agreed, I just said the same elsewhere. Early computing was filled with memory and compute limitations that meant having every language under the sun supported was just not physically possible.
blåhaj.com is a thing, why not blåhaj.zone? It's possible.
In DNS, the domain name has to be ASCII, so unicode characters in the domain name are converted to Punycode and prefixed with
xn--
. So really, blåhaj.com is reallyxn--blhaj-nra.com
(put that in your browser and watch the name change).I would imagine that most things would just work, but there would probably be some annoying bugs with different clients who aren't using libraries which support internationalized domain names, or aren't expecting them. It'd probably be a good thing to have an internationalized domain name for a popular instance, as that would be a good test case for servers and clients to support that standard.
I'm personally convinced limitations like this are why English is becoming such a dominant language, because the internet and most coding was all designed in English for English, without consideration for other languages. Other languages have to get tacked on with semi-complicated workarounds like this.
All of this stuff is 50 years old and there's no way the people who put these systems in place could have ever predicted the Internet as it is today. Famously in 1973, there was a "map of the ARPA network", that's how few machines were "online" at the time.
It's really only in the past 10 years or so that security via TLS has been widely adopted by websites, and it's been over 20 years since IPv6 was announced and still is not entirely supported everywhere. There is so much inertia with the underlying infrastructure of the internet, even if there is a serious issue (like DNS cache poisoning ), systems will not be reworked and replaced, but hacks will be added to fix the issue of the day.
Agreed, I just said the same elsewhere. Early computing was filled with memory and compute limitations that meant having every language under the sun supported was just not physically possible.