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

Forwarded to devs additional zone for subdomains after update

Dmytro

Basic Pleskian
Hi.
Not sure if it's related, but I can't find any other reasons

Today I did update to Plesk Obsidian 18.0.57 update 4 (CloudLinux 8.7)
And now if I add new subdomain - I receive request to create new zone for this subdomain on Slave, but it should be only refresh for domain

Code:
received control channel command 'addzone subdomain.domain.com IN  { type slave; file "subdomain.domain.com"; masters { 9.8.5.9; }; };'

I have also Plesk Obsidian 18.0.55 update 2 CloudLinux 8.8 - and there is no such problem, also
 
here is more detailed dns log from slave:

Code:
Dec 19 22:38:11 ns1 named[5608]: received control channel command 'addzone subdomain.domain.com IN  { type slave; file "subdomain.domain.com"; masters { 1.5.9.9; }; };'
Dec 19 22:38:11 ns1 named[5608]: zone subdomain.domain.com added to view _default via addzone
Dec 19 22:38:11 ns1 named[5608]: zone subdomain.domain.com/IN: refresh: NODATA response from master 1.5.9.9#53 (source 0.0.0.0#0)
Dec 19 22:38:12 ns1 named[5608]: received control channel command 'refresh subdomain.domain.com IN '
Dec 19 22:38:12 ns1 named[5608]: zone subdomain.domain.com/IN: refresh: NODATA response from master 1.5.9.9#53 (source 0.0.0.0#0)
Dec 19 22:38:12 ns1 named[5608]: received control channel command 'refresh domain.com IN '
Dec 19 22:38:13 ns1 named[5608]: zone domain.com/IN: Transfer started.
Dec 19 22:38:13 ns1 named[5608]: transfer of 'domain.com/IN' from 1.5.9.9#53: connected using 7.8.9.3#48879
Dec 19 22:38:13 ns1 named[5608]: zone domain.com/IN: transferred serial 2023121924
Dec 19 22:38:13 ns1 named[5608]: transfer of 'domain.com/IN' from 1.5.9.9#53: Transfer completed: 1 messages, 25 records, 1157 bytes, 0.038 secs (30447 bytes/sec)

and I have two zones in config:

zone domain.com { type slave; file "domain.com"; masters { 1.5.9.9; }; };
........
zone subdomain.domain.com { type slave; file "subdomain.domain.com"; masters { 1.5.9.9; }; };

but there is no file file "subdomain.domain.com" , only file "domain.com"

and file file "domain.com" has A record about subdomain.domain.com
 
I talked with Plesk support and they reproduced this on their test environment, so we are waiting for bug fix
 
As I know, there is no fix for today. But you can activate "own zone creation" for subdomains using this command:

Code:
plesk bin server_pref -u -subdomain-dns-zone own

Be aware, this will run through all your subdomains and recreate zones for them
 
Hi. I see related Fix in last changelog (PPPM-14316) . Is this fix for described here problem?
 
Has anyone found a temporary solution? It's still NODATA at slaves... :(
Ah! There is a temporary workaround. We can Enable (switch to local dns service) in subdomain and then it became resolvable.
1. go to subdomain
2. enter DNS
3. click Enable
 
Back
Top