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

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