• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved IDN Domain Routing (Resolving Domainname) Problem

GeeBee

New Pleskian
IDN Domains are not resolved, causing a 403 error in Browser

Forbidden
You don't have permission to access / on this server.


OS:
Plesk Onyx Version 17.5.3 Update #6
Ubuntu 16.04.2 LTS‬

Domain was set with IDN coding but this should not be issue since other similar server running on Plesk 12.5 and Ubuntu 14 dont have this problem.
 
Have you tried to fix it with

# plesk repair fs
# plesk repair web

?
 
My assumption was wrong. The problem was not connected to Plesk.

I transferred the domain and changed the IP address pointing to the server running with Plesk. I was used to have a stable routing after minutes. But with the IDN domain it took two full days. After that time the problem vanished. So nothing to do with Plesk, more with the fact that nameserverrouting ist not fully stable in the process of domain transfer and takes ages for IDN domains.
 
Back
Top