• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Question ds record base64 key

nMLxTMJTZ

Regular Pleskian
Server operating system version
ubuntu 24.04
Plesk version and microupdate number
18.0.69
Hi, when i try to add DS record in my OVH panel for my domain i give error "Public key should be encoded in Base64" where i can found it?
 
Did you generate the DNSSEC settings for the domain? You need to make sure you select the right DS Data Algorithm, Digest Type, and set the right Key Tag. The digest will be the data which is the info. The generated key for the DS should be Base64 already and you can verify by using Base64 Validator | Tools | Base64 to validate it.
 
Just to make sure, you used the Plesk DNSSEC extension to generate the DNSSEC records on the domain then logged into the registrar (where you registered the domain) to add the generated records? Because the records you get from the extension is meant to be inserted where you've registered the domain on, not where you manage the DNS records. So if the DNS records is managed by OVH (and not on your Plesk server) and your registrar is somewhere else, then you would need to make the DNSSEC record from OVH to install with the registrar. If the DNS is actually managed by your Plesk server then you will want to make sure the that the name servers on the registrar actually points to your server and the DNSSEC entries generated and install the digest info into whoever the registrar is.
 
yes i done this, DNSSEC extension, record on OVH but i have this problem "The server responded with DNSKEY but not with expected NSEC or NSEC3." now but also DNS sec work
1744962907650.png
 
I wouldn't worry as long as everything else checks out fine then. You know if it's a problem if it's not resolving DNS at all.
 
Back
Top