Slave DNS error

[Chris1]

I am using the Slave DNS manager and I'm getting the following error in /var/log/messages on the slave server when the master/plesk tries to send change notifications.

received notify for zone 'example.com': not authoritative

The domain is pointing to ns1.mydomain.com and ns2.mydomain.com, the domains zone on the master has both of these as NS records. And the SOA record lists ns1.mydomain.com as the primary authoritative nameserver.

The zone has not been set on the slave server, what would be the cause here?

Slaves named.conf
bbb.bbb.bb.bbb = Slave IP
aaa.aa.aa.aaa = Master/Plesk

options {
  listen-on port 53 { 127.0.0.1; bbb.bbb.bb.bbb; };
  listen-on-v6 port 53 { ::1; };
  directory  "/var/named";
  dump-file  "/var/named/data/cache_dump.db";
  zone-statistics yes;
  statistics-file "/var/named/data/named_stats.txt";
  memstatistics-file "/var/named/data/named_mem_stats.txt";
  allow-query  { any; };
  allow-new-zones yes;
  recursion no;

  dnssec-enable yes;
  dnssec-validation yes;
  dnssec-lookaside auto;

  /* Path to ISC DLV key */
  bindkeys-file "/etc/named.iscdlv.key";

  managed-keys-directory "/var/named/dynamic";

  pid-file "/run/named/named.pid";
  session-keyfile "/run/named/session.key";
};

key "rndc-key" {
  algorithm hmac-md5;
  secret "xxxxxxxxxxxxxxxxxxxxxxxxx";
};

key "rndc-key-aaa.aa.aa.aaa" {
  algorithm hmac-md5;
  secret "xxxxxxxxxxxxxxxxxxxxxxxxx";
};

controls {
  inet * port 953
  allow { aaa.aa.aa.aaa; 127.0.0.1; } keys { "rndc-key"; "rndc-key-aaa.aa.aa.aaa"; };
};


logging {
  channel default_debug {
  file "data/named.run";
  severity dynamic;
  };
};

zone "." IN {
  type hint;
  file "named.ca";
};

include "/etc/named.rfc1912.zones";
include "/etc/named.root.key";

 

[Chris1]

Is it advising it is not authoritative because the config for this domain is not listed in in /var/named/3bf305731dd26307.nzf?

If so, why would it not be automatically creating the entry in there all of a sudden?

 

[Chris1]

This problem appears to be resolved. I removed the Slave DNS manager and then re-installed it and that seemed to fix the issue.