IIS7 - Configuration & Scripting

Re: Configuring binding for international domains, IDN

Műmaǳagkötő — Thu, 17 Sep 2009 17:58:12 GMT

Hi,

There are limited and restricted elements on IDN coding-decoding. For example, the section of mathematical equation signs of Unicode, currencies etc. are restricted. It is normal blocked name. (An other example is in my nickname. It is included in my national alphabet, but this time categorized as limited. )

The dotCOMcom registsry runs internationally, like dotNET and dotORG runs. But not all of ccTLDs providing "non-LDH" registry.

There are supranational ccTLDs, where the IDN-encoding/decoding is "Under developement". The dotEU uses "multi-script" IDN, and the dotASIA have a different structure for its root but plans IDN. (An other rule on PUNY, that mixed scripts - means mixed writing signals of different alphabets - should be rejeced in registering phase.)

There are Latin scripts where the X is not element in the alphabet, so the collation rules regulation is leaking. The example.security.pl structure is typical leak, the X (0058) is not member of Polish alphabet.

Re: Configuring binding for international domains, IDN

JeongHwan — Mon, 08 Sep 2008 21:52:36 GMT

Sorry to be late to reply.

It seems to be the product issue of IIS 7 UI. I am going to investigate more for the issue.

You can update applicationhost.config directly as work-around.

Or, if you have installed the configuration editor, which is one of the IIS Admin Pack features, you can set the GB£.com string with it.

1. Open Inetmgr.exe

2. Select Server tree

3. Double-click "Configuration Editor" icon of the middle pane window

4. Type "system.applicationHost/sites" onto "Section:" dropdown control

5. Expand "(collection)" property by clicking "..." button which is by the property

6. Select the target site item

7. Expand "bindings" property by clicking "..." button which is by the property

8. Update the binding information to "*:80:GB£.com" from "*:80:"

9. Close all the collection edior dialog and click "Apply" task which is under the Configuration Editor's Actions group.

Re: Configuring binding for international domains, IDN

idn_names — Wed, 20 Aug 2008 19:08:07 GMT

Hi,

I am experiencing the same problem with my domain .xn--gb-cda.com (GB£.com) but cannot enter the name in either format as it contains the '£' (british pound currency symbol).

I tried the above domain www.åäö.se as a test and it worked fine, but mine returns the error 'The specific host name is invalid. The valid characters are A-Z, a-z, 0-9, - and _.'

Why does IIS7 accept the .se domain that clearly contains characters out of the error message range, but not mine that contains a '£'?

Re: Configuring binding for international domains, IDN

JeongHwan — Mon, 11 Aug 2008 22:23:28 GMT

Hi,

In IIS7, we should use domains like "www.åäö.se" for web binding unlike in IIS6.

So, please try to using "www.åäö.se" string value for the binding information instead of using "www.xn--4cab6c.se" and it will work.

Configuring binding for international domains, IDN

Todii — Sat, 09 Aug 2008 16:12:44 GMT

Hi!

I recently ran into a problem trying to add a binding for an internation domain name, IDN, containing characters like ÅÄÖ.

In IIS 6, you could not add domains like "www.åäö.se", you had to add the PUNYCODE instead, which is "www.xn--4cab6c.se". I was trying to migrate my sites over to IIS7 on Windows server 2008, and naturally i tried to add the same binding. But after doing that, it was impossible to start the site. I only got the error "Value does not fall within the expected range.". After some testing i found that you get this error when trying to start a site containing a binding with the character combination "xn--" in it.

However, it is apparently now possible to add a binding right away to "www.åäö.se", bypassing the punycode altogether. Atleast that seems to work for me.

Could someone with insight into the inner working of IIS7 tell me why i get this crappy error that tells me nothing, and if i should be using the "www.åäö.se" binding instead, will that work as expected?

Thanks!