• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Issue Bug in latest update? DNS changes nog propagated

Tozz

Regular Pleskian
Hi there,

We are seeing an issue on multiple of our Plesk machines whereby DNS zonefile changes are not propagated to bind/named.
The zonefile in /var/named/run-root/var/<domain> doesn't get updated by Plesk after the customer makes a change in their zonefile.

Running 'plesk repair dns' fixes the issue (the zonefiles are updated) but subsequent changes still suffer from the same issue.

Is this a known bug in the latest update? (We have auto-updates on)

OS Debian 10.10
Product Plesk Obsidian
Version 18.0.38 Update #3, last updated on Oct 6, 2021 06:26 AM
 
Back
Top