• 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.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • 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.

Resolved Event "DNS zone updated" still fired for domain alias when DNS zone synchronization with primary domain is disabled

Kaspar

API expert
Plesk Guru
Username:

TITLE

Event "DNS zone updated" still fired for domain alias when DNS zone synchronization with primary domain is disabled

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

AlmaLinux 8.6, Plesk 18.0.45

PROBLEM DESCRIPTION

The event Default domain, DNS zone of domain alias updated from the Event Manager is still fired when the DNS zone of the primary domain is modified but the option "Synchronize DNS zone with the primary domain" for the alias domain was switched off.

STEPS TO REPRODUCE

  1. Add a subscription
  2. Add domain alias to subscription
  3. Switch "Synchronize DNS zone with the primary domain" option off
    wPWvnvO.png
  4. Create simple bash script which logs the the event (see my example below) to run when event is fired.
  5. Create "Default domain, DNS zone of domain alias updated" event in event manager to run script created in previous step.
  6. Go to DNS settings of primary domain and change or add some records for testing purposes and apply changes.
  7. View the /tmp/tmp.log file (or whichever log methode you've used) and notice how there is an log entry for the domain alias.

Bash:
#!/bin/bash
# Set permission for script: chmod +x test-event.sh

touch /tmp/tmp.log
echo "Event fired for domain ${NEW_DOMAIN_ALIAS_NAME}" >> /tmp/tmp.log

ACTUAL RESULT

The event "Default domain, DNS zone of domain alias updated" gets fired when the DNS zone of the primary domain gets updated.

EXPECTED RESULT

It's expected that the event "Default domain, DNS zone of domain alias updated" does not fired as synchronization with primary domain is disabled.

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Fixed in Plesk Obsidian 18.0.46:
The Event Manager “Default domain, DNS zone of domain alias updated” event no longer triggers when the DNS zone of a domain with one or more domain aliases with the “Synchronize DNS zone with the primary domain” option disabled is modified. (PPPM-13646)
 
Back
Top