<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 11/03/2019 11:41, 姜伯洋 wrote:<br>
</div>
<blockquote type="cite"
cite="mid:3c52d93b.da6a.1696c8ee44d.Coremail.15555513217@163.com">
<div><br>
</div>
<div>I always see this error on the API monitoring page of the
8081.</div>
</blockquote>
<p>In the private E-mail you sent, you included the image:</p>
<p><img src="cid:part1.D862B11D.F1F86DBD@pobox.com" alt=""></p>
<p>"Unable to queue notification of domain 'test.org': nameservers
do not resolve!"</p>
<p>There's your error. Your master authoritative server needs
access to a working DNS cache in order to send notifications to
the hosts listed in NS records. By default it will be doing this
via /etc/resolv.conf</p>
<p>Unfortunately I don't think it's possible to point
/etc/resolv.conf to a nameserver other than on port 53. But you
can instead use the "<a moz-do-not-send="true"
href="https://doc.powerdns.com/authoritative/settings.html#resolver">resolver</a>"
option to point it to your local recursor on port 5300.<br>
</p>
<p>You will make your life much, much easier if you have a separate
recursor. Even simpler, just remove the recursor from all your
authoritative servers, and in /etc/resolv.conf point to a public
caching server such as 1.1.1.1 / 8.8.8.8 / 9.9.9.9.</p>
<p>(By "much, much easier", I mean that it's extremely hard to
administer a Linux system if /etc/resolv.conf is not pointing to a
working caching nameserver, so you need to fix that anyway)<br>
</p>
<p>On a separate point: if you are using mysql for your backend, you
can simply use mysql replication between your hosts; this works
very reliably and avoids a load of potential problems with
master-slave zone transfers.</p>
<p>Regards,</p>
Brian.
</body>
</html>