• 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 New Domain - Digital Ocean DNS Enabled by Default

Daniel Hendricks

Daniel Hendricks

New Pleskian
Is there a way to make new domains sync with DigitalOcean DNS (via the extension) by default?

Currently, when I create a new domain, it appears that I have to activate it manually.

P2wkQp.jpg
 
It appears that this is not possible with the extension, which doesn't make it suitable for automatic provisioning. I removed it and am using the Slave DNS Manager extension now.
 
Hi Daniel Hendricks,

Now it is possible. The behavior is improved in the latest release:
DigitalOcean DNS 1.1.0
  • Newly created domains are now automatically activated in DigitalOcean DNS.
  • In Plesk 17.9, the icons on the “DNS management” tab are now displayed correctly. (EXTPLESK-741)
Click to expand...
 
You must log in or register to reply here.

Similar threads

B
Issue Slave DNS servers not updating zone from target server after migrating domain from source server.
Replies
3
Views
759
BigBlock
B
R
Issue Let's Encrypt Error 400 on every domain
Replies
1
Views
795
Sebahat.hadzhi
Sebahat.hadzhi
A
Question Cloudflare DNS extension & /usr/local/psa/admin/bin/dnsmng --update
Replies
3
Views
707
AYamshanov
AYamshanov
T
Resolved Digital Ocean DNS extension doesn't sync MX records TTL
Replies
2
Views
1K
AYamshanov
AYamshanov
J
Question Enable DNS Caching with Plesk Firewall extension in use
Replies
1
Views
559
Kaspar
K
Back
Top