• 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!
  • 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 DNS slave error

layerwire

Basic Pleskian
Hi, already created ticket, but maybe someone else had same issue.
We are using Debian 7.

Code:
Jan  4 13:54:35 debian named[4116]: transfer of 'domain.com/IN' from 40.69.41.224#53: connected using 10.0.2.4#44783
Jan  4 13:54:36 debian named[4116]: transfer of 'domain.com/IN' from 40.69.41.224#53: failed while receiving responses: NXDOMAIN
Jan  4 13:54:36 debian named[4116]: transfer of 'domain.com/IN' from 40.69.41.224#53: Transfer completed: 0 messages, 0 records, 0 bytes, 0.202 secs (0 bytes/sec)
 
Last edited:
Hi, already created ticket, but maybe someone else had same issue.
We are using Debian 7.

Jan 4 13:54:35 debian named[4116]: transfer of 'domain.com/IN' from 40.69.41.224#53: connected using 10.0.2.4#44783
Jan 4 13:54:36 debian named[4116]: transfer of 'domain.com/IN' from 40.69.41.224#53: failed while receiving responses: NXDOMAIN
Jan 4 13:54:36 debian named[4116]: transfer of 'domain.com/IN' from 40.69.41.224#53: Transfer completed: 0 messages, 0 records, 0 bytes, 0.202 secs (0 bytes/sec)

try to use it I think it will be work for you
This is my.named.conf on my secondary DNS (ISPConfig)
zone "domain.org" {
type master;
file "domain.zone";
allow-transfer {195 ... ... ...; };
};
just make sure your firewall not blocked port tcp/ip
 
try to use it I think it will be work for you
This is my.named.conf on my secondary DNS (ISPConfig)
zone "domain.org" {
type master;
file "domain.zone";
allow-transfer {195 ... ... ...; };
};
just make sure your firewall not blocked port tcp/ip
Thanks for advice, port 952 was closed. Now then its open we are getting same error plus this new one


Code:
root@admin:/var/log/bind# telnet 40.**.**.224 953
Trying 40.**.**.224...
Connected to 40.**.**.224.
Escape character is '^]'.
 
Back
Top