Skip to main content

Custom Domain Publishing, And World Culture

People who speak (read / write) languages, that do not use Roman character sets, need to publish in their native language - and the Internet now supports that need.

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.

There may be limitations, though.

Here is a blog published to "www.राजभाषाअनुभाग.भारत" - aka "www.xn--l1b0bn3cxacq2d2ccbd1b.xn--h2brj9c".







Houston, we may have a problem with TLDs that are IDN encoded.

For a TLD that is in English ("بحث-سناب.com"), both of these work:

http://www.digwebinterface.com/?hostnames=xn----zmcbcml8b0j.com%0D%0Awww.xn----zmcbcml8b0j.com&type=A&useresolver=8.8.4.4&ns=auth&nameservers=

https://intodns.com/xn----zmcbcml8b0j.com

For a TLD that is IDN encoded (राजभाषाअनुभाग.भारत"), we have mixed success.

This works:

http://www.digwebinterface.com/?hostnames=xn--l1b0bn3cxacq2d2ccbd1b.xn--h2brj9c%0D%0Awww.xn--l1b0bn3cxacq2d2ccbd1b.xn--h2brj9c&type=A&useresolver=8.8.4.4&ns=auth&nameservers=

This does not work:

https://intodns.com/check/?domain=%E0%A4%B0%E0%A4%BE%E0%A4%9C%E0%A4%AD%E0%A4%BE%E0%A4%B7%E0%A4%BE%E0%A4%85%E0%A4%A8%E0%A5%81%E0%A4%AD%E0%A4%BE%E0%A4%97.%E0%A4%AD%E0%A4%BE%E0%A4%B0%E0%A4%A4



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

Comments

Popular posts from this blog

Custom Domain Migration - Managing The Traffic

Your blog depends upon traffic for its success.

Anything that affects the traffic to your blog, such as any change in the URL, affects the success of your blog. Publishing the blog to a custom domain, like renaming the blog, will affect traffic to your blog. The effects of the change will vary from blog to blog, because of the different traffic to every different blog.Followers. People who find your blog because of recommendations by other people.Search engines. Robotic processes which methodically surf your blog, and provide dynamic indexing to people who search for information.Subscribers. People who read your content from their newsfeed reader, such as the dashboard Reading List.Viewers. People who read your content from their browser.No two blogs are the same - and no two blogs will have the same combinations of traffic sources.

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.