Unable to assig IP address to website. Contains non LDH characters.

Created:

2016-11-16 12:57:26 UTC

Modified:

2016-12-21 19:37:47 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Unable to assig IP address to website. Contains non LDH characters.

Symptoms

Unable to assign IP address to website. The following error appears:

>"%plesk_bin%"\\websrvmng.exe --set-default-domain --ip-address=1.1.1.1 --vhost-name=example.com

Contains non LDH characters
In rdidna module
Exception type: realdev.net.idna.IDNAException
at realdev.net.idna.DnsIDNA.toASCII(String input, Boolean allowUnassigned, Bo
olean useSTD3ASCIIRules)
at realdev.net.idna.DnsIDNA.toASCII(String input)
at IIS7WebSite.get_bindings(IIS7WebSite* , list<WebSiteBinding\\,std::allocato
r<WebSiteBinding> >* )

Cause

  1. Special symbols being used in DNS records/zones.
  2. Forged hostnames in IIS bindings.

Resolution

  1. IDNA standard allows DNS records to contain only letters/digits/hyphens.

Chech DNS TXT records for domain on errors:

    >cd "%pelsk_dir%"
>cd MySQL\\bin\\
>mysql -uadmin -p -P8306 psa -Ne"select id,val from dns_recs where type='txt' and val!='v=spf1 a mx ~all' and val!='o=-';"

| 26761 | v=spf1 a mx include:example.com ~all
| 26776 | google-site-verification=4WBJ1dawyI0b7kLa_SrEAbkC_3kJ3YcTxewyJRLpbU4|
| 26819 | v=spf1 a mx include:example.com ~all|
| 27034 | v=spf1 a mx include:example.com ~all|
| 27048 | v=spf1 a mx include:example.com ~all|
| 27052 | v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCO+lQCbHQpf4Ox
EnjUbeVtlx+5oDFO8uzEXCKgnbdbVCG41pRU/ZOYYBmBr4KKoq2yMJOl3qZZ0kH1DYtHA0AWT9QMioxS
G9/XynnA2R1GLpzcbtT4vP8O8xC3gyZOTmgkYq8lY6W8JDC5HaoJPAGJgMcphzIS4sH3dx7Ru/XN/wID
AQAB|
| 27062 | v=spf1 a mx include:example.com ~all|
| 27076 | v=spf1 a mx include:example.com ~all|
  1. The issue may be caused by forged hostnames in IIS bindings for websites.
    IIS Manager -> site_name -> Bindings

For some bindings there are custom host names like domain-name_old , with "_" sign that cannot be used in domain names. Such changes could be done in IIS manually as Plesk would not allow such configuration.

Remove such host names from IIS and rerun IP assigning task.

Have more questions? Submit a request
Please sign in to leave a comment.