H
henken
Guest
Sad that many people don´t see the real problem behind this issue. Even if RFC is only a recommendation and not mandatory, the DNS service of Plesk should and must be RFC compliant. Many ISPs and also Domain Registries with their nameservers support only the YYYYMMDDnn format. Now if you´re running Plesk as a master for your zones and an ISP slave we get a problem with following example:
The ISP is member of several domain registries. The customer of the ISP who is running his Plesk as a primary for his new domains he wants to register through the ISP would bring up the following issue at least with the german registry Denic.
Try to register and/or update a domain, where you specify the Pleskserver as Primary and the ISP as slave server you´ll receive an error, because the german registry robot says:
Warning, the serial number does not meet the YYYYMMDDnn format, register/update not success.
So much for a Unix Timestand is sufficient! WHICH is NOT!!
Thanks!
SW-Soft: Get working guys. Hotfix needed urgently!!! The community will not stop bugging until you get it sorted
The ISP is member of several domain registries. The customer of the ISP who is running his Plesk as a primary for his new domains he wants to register through the ISP would bring up the following issue at least with the german registry Denic.
Try to register and/or update a domain, where you specify the Pleskserver as Primary and the ISP as slave server you´ll receive an error, because the german registry robot says:
Warning, the serial number does not meet the YYYYMMDDnn format, register/update not success.
So much for a Unix Timestand is sufficient! WHICH is NOT!!
Thanks!
SW-Soft: Get working guys. Hotfix needed urgently!!! The community will not stop bugging until you get it sorted