• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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