• 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.

Request: Make the DNS RFC compliant!!

H

henken

Guest
Dear SW-Soft,

i hope you know that by not following RFC rules, it can and will force upcoming problems for your customers, if they are using Plesk as a primary DNS server with registries.

While Plesk hosts the primary DNS zone, we use a second and third nameserver that are working as slave. Now we stumbled into a problem, that we cannot apply domainupdates or domain registrations with different Registries, because of the UNIX timestamp format. They not only recommend but do force their customers to use the format "YYYYMMDDnn" which Plesk does NOT support for whatever reason I don´t really understand.

RFC are mostly recommendations, but they were made for a reason!!!

Sorry for this kinda rant, but i´m currently a bit steamed about such a small issue where SW-Soft doesn´t seem to get a solution coded at least for Linux! :mad:

And i´ve searched this forum and so far not a single solution for this kinda small issue :(
 
dnsstuff.com tells me:

Your SOA serial number is: 1178109784. That is OK, although the recommended format (per RFC1912 2.2) is YYYYMMDDnn, where 'nn' is the revision. (...)

Your SOA serial appears to be the number of seconds since midnight 01 Jan 1970 when the last DNS change was made (tinydns format). (...)

So yeah, YYYYMMDDnn is the recommended format, but I think that registries that force you to use YYYYMMDDnn and don't allow the tinydns/djbdns/UNIX timestamp format are acting silly. AFAIK (I haven't read the RFC lately) the only real requirement is that your SOA serial increases every time a change is made to the zonefile.

P.S. This is still a valid request of course. Please use the 'Suggestions and Feedback' forum instead of this 'How Do I' forum.
 
Back
Top