• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

underscore in domain name

John W

Basic Pleskian
Couple of customers have underscores in their domain names (worked on a different server for the past 15+ years), but Plesk refuses to accept them. Is there a workaround? Thanks.
 
I suppose that this is due to meet the requirements of the document RFC952:

1. A "name" (Net, Host, Gateway, or Domain name) is a text string up
to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus
sign (-), and period (.). Note that periods are only allowed when
they serve to delimit components of "domain style names".
 
Plus all the domain name registrations I went to removes the underscore when I tested, which just goes back to the requirements of RFC952 that IgorG posted. You might want to make sure that sure that they didn't mean dash.

The only time I see an underscore in the domain is when setting up a SRV record (autodiscover_._tcp.domain-name.com) or as a TXT record for a domain key. Is this what you might mean? if so, it would be added as a DNS record and not as a domain.
 
Back
Top