Some registrars will register domains which use non Roman character sets, in the URL. Not all Internet services will accept non Roman characters, however.
My favourite online DNS diagnostic services, DigWebInterface, and intoDNS, and Rex Swain's HTTP Viewer, only use ASCII. One cannot use non ASCII ("non Roman") characters, with either service.
"بحث-سناب.com", as converted, shows an example of an Internationalized domain name.
To use DigWebInterface to retrieve DNS addresses, and intoDNS to check the domain setup, we have to convert the native URL to Ascii.
I use three reliable online services, which will convert URLs to ASCII.
Converting "بحث-سناب.com" to ASCII involves use of one of the latter services.
DomainTools
WhoIs - Identity for everyone
Who.is - Powered by Name.com
Using the 3 tools, we see that "بحث-سناب.com" == "xn----zmcbcml8b0j.com", "XN----ZMCBCML8B0J.COM", and "xn----zmcbcml8b0j.com", respectively. Look carefully, in the body of the display for each service, for the IDN equivalent.
We can then use "xn----zmcbcml8b0j.com", with DigWebInterface, and intoDNS - and get the necessary diagnostics.
And using the latter tools, we see a properly setup domain - which is now being used for a properly published Blogger blog, verified in Rex Swain.
DigWebInterface
intoDNS
Rex Swain's HTTP Viewer
And when assistance is requested, in Blogger Help Forum: Get Help with an Issue, we can use these tools with non Roman character URLs.
The Internet now supports use of non ASCII characters, in URLs. In order to publish #Blogger blogs to Internationalised Domain Names, we need to convert native URLs to ASCII - using any one of three identified online DNS services.
https://productforums.google.com/forum/#!category-topic/blogger/qKWZ0807m60
https://productforums.google.com/forum/#!category-topic/blogger/L1pv6CPUK18
Posts
No comments:
Post a Comment