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

Question Azure DNS Feedback

S

sjdean

New Pleskian
Server operating system version
Ubuntu 20.04
Plesk version and microupdate number
18.0.44
We are an organisation that handled both development and technical clients. As such, we need to be able to handle domain names where we can set MX for O365, or A/CNAME records that point to third party infrastructure, as well as other SRV resource usage information for Skype/Teams etc.

Azure DNS looked like the perfect thing, however, it looks like all this does is merely sync the records on the web server to Azure DNS. Thankfully it only updates Azure DNS after the plugin has been enabled and records have been saved to the DNS Zone on Plesk.

Understandably, this is unsuitable for us, and also causes the other problem, as we host DNS records in Azure, when LetsEncrypt comes along to renew a wildcard certificate, it generates a new _acme-challenge token which can never be updated, unless you have Azure DNS and don't mind your DNS records overwritten.

So:

  1. You need to make clear in your Azure DNS documentation that this is a ONE WAY sync only, from Plesk to Azure. It is not bidirectional.
  2. Need some updates to the Azure DNS plugin and I would suggest:
    1. Need to allow Azure DNS to be Primary DNS and for Azure DNS records to be sucked into Plesk.
    2. What would take a great amount of work but would be fabulous - bidirectional sync with advisement of conflicting changes - so it doesn't matter what you updated and where, it would automatically pick the right data to transfer.
Simon
 
Hi sjdean,

Thank you for your feedback.

1. Sorry to hear that documentation is confusing here. It is true, extensions provide a one-way synchronization, from Plesk to any 3rd-party DNS service (which could be connected via existing Plesk extension). I mean it is not a limitation of AzureDNS extension only, it is how integration works in Plesk.
I will ask our tech.doc department to add more details in extensions' descriptions to make this limitation more visible.


2. In the case of a bidirectional synchronization, it is really sound like a feature request and I would suggest creating a new request via UserVoice.
 
You must log in or register to reply here.

Similar threads

C
Question Plesk with Cloudflare Proxy DNS Records and Letsencrypt..
Replies
0
Views
1K
cpulove
C
Hangover2
Question Update specific nameserver for all domains
Replies
1
Views
807
Kaspar@Plesk
Kaspar@Plesk
N
Issue Reconfigurator slow performance when adding DNS records
Replies
0
Views
921
nelteren
N
S
Resolved Azure DNS access token
Replies
3
Views
2K
SimonB
S
M
Issue Letsencrypt not automatically updating certificate
Replies
0
Views
1K
mr-wolf
M
Back
Top