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

Issue DNS: failed while receiving responses: NOTAUTH

L

leon1811

New Pleskian
Hey,

I have one new plesk other with a DNS Problem. When I add new domains to the panel, I have to run every time "plesk repair dns -y". Without that, the domain is not resolvable.

Slave DNS Server returns:
transfer of 'XXXXX/IN' from 123.123.123.123#53: failed while receiving responses: NOTAUTH
[....]
zone test-XXXXX/IN: refresh: unexpected rcode (REFUSED) from master 123.123.123.123#53 (source 0.0.0.0#0)


Version 18.0.54 Update #4, Debian 11.7
 
This could mean that your Plesk server was not entered as one of the authoritative nameservers into the domain name dataset when you registered the domain name.
 
Also on the master/plesk server the dns zone is not created successfully.
On the plesk server "dig @localhost DOMAINNAME" only works after "plesk repair dns -y". Before that the domain name could not be resolved. That should also work --> and that works on my other plesk servers with not (nic) registered domains.
 
Have you verified that your authoritative nameservers have been entered correctly into the domain dataset?
 
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
680
BigBlock
B
N
Issue cPanel to Plesk migration problems
Replies
6
Views
2K
Kaspar@Plesk
Kaspar@Plesk
enerspace
Forwarded to devs Slave DNS manager does not transfer subdomains
Replies
10
Views
2K
Dave W
Dave W
Dmytro
Forwarded to devs additional zone for subdomains after update
Replies
16
Views
3K
Dmytro
Dmytro
P
Issue DNS answer without authority
Replies
0
Views
957
p0se
P
Back
Top