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

Resolved DNS sync delivers strangely formatted zonefiles after 17.8 update

kenneth-vkd

Basic Pleskian
Hi
We have been running Plesk Onyx 17.5 for Windows for some time and have been using the "Slave DNS Manager" extension to sync DNS zones to our nameservers.
However after we have updated Plesk to 17.8.11, the zones transferred look really strange on our linux-based nameservers. Opening the files in Wordpad on the windows server does not indicate any issues.
We have tried to run "plesk repair dns", but no luck.
There seems to be some kind of issue with the encoding of the file and therefore the nameservers are using an old cached version of the zone.
Skærmbillede 2018-05-25 kl. 17.28.32.png

As a test, I tried to delete one of the zones and resync from Plesk, but no luck. The issue persists across all our 4 nameservers

Does anyone else experience similar issues with the DNS sync after the update and know how to fix it?
 
I tried running hamed-compilezone to see if this would correct an affected zone. However, it seems as if the zone on the Plesk server is not in "raw" format, as it fails when trying to convert from raw to text. Running the same procedure on one of our nameservers did however run succesfull for a specific affected domain and the zone file is now readable.
It must however have something to do with the recent plesk update, as it was stored in text format before upgrade from 17.5 to 17.8.
Could it have something to do with RNDC?
 
Usually, Plesk works as master DNS-server. The zone-file format was changed only for slave DNS-server; so, I think this not dependent on what Plesk version installed. Did you change a version of BIND on slave DNS-server in past? Anyway, you can configure "masterfile-format text" clause in the config of slave DNS-server.
 
makes a copy of the bind files, now once this copy is done, rename them and regenerate the files with the repair bind and problem solved.
 
Just changed the named.conf on the external nameservers to force them to be saved as text as mentioend by AYamshanov and it generates the files correctly.
But seems strange that this started right after upgrading from Plesk 17.5 to 17.8
 
Back
Top