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

Forwarded to devs Transfer of DNS Records Ext - picks wrong domain

TomBoB

Silver Pleskian
Username:

TITLE

Transfer of DNS Records Ext - picks wrong domain

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk 18.0.57 #5, AlmaLinux 8.9, Transfer of DNS Records ext vers 1.1.2-129

PROBLEM DESCRIPTION

A few conditions need to be met.
Have Transfer of DNS Records extension installed. Attempt to export DNS settings of an Alias. Alias needs to have "Synchronize DNS zone with the primary domain" disabled.

STEPS TO REPRODUCE

Have Transfer of DNS Records extension installed.
Pick a domain Alias of some domain.
Disable "Synchronize DNS zone with the primary domain".
Go to Alias its DNS settings and attempt to "Transfer DNS"

ACTUAL RESULT

Picks a random domain, instead of the Alias its domain name, to export.

EXPECTED RESULT

Picks the domain Alias it's domain and settings

ANY ADDITIONAL INFORMATION

Cloudflare DNS extension can't export Alias' DNS settings yet.
Discovered above when looking for a quicker way to get the DNS transfer done then just manually adding everything to Cloudflare.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
It's 9 month later, any light at the end of the tunnel?
Moving domains / aliases and still same issue.
 
A fix for that issue has not been introduced yet. We understand that the resolution might be taking more than expected and we would like to apologize for the inconvenience. It is on team's agenda, but there are more pressing and critical issues prioritized. Thank you for your patience and understanding in the meantime.
 
Back
Top