• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

DNS SOA RNAME field problem

P

pegasus

Guest
We recently discovered that certain domain names do get rejected at our registrar testing process. The reason is always parsing of the mail address plesk puts in the soa record (RNAME field).

If user puts his email address as [email protected], plesk happily writes name.surname.somedom.ain into the bind zone. Then, when the domain goes through a check at the registrar, their script parses it as [email protected], cannot find the mx for it and reports an error.

Possible solutions:

1. (bad) force the user to enter a mail address without the dot left of @
2. (good) properly escape the dot in the bind zone file as name\.surname.somedom.ain
3. (good) use [email protected] as recommended by rfc2142 paragraph 7 and automatically set up alias for hostmaster to point at that user.

Right now we have to live with first solution ... so when can we expect a fix?
 
Back
Top