On 11/03/2019 11:41, 姜伯洋 wrote:
I always see this error on the API monitoring page of the 8081.
In the private E-mail you sent, you included the image:
"Unable to queue notification of domain 'test.org': nameservers do not
resolve!"
There's your error. Your master authoritative server nee
On 11/03/2019 11:15, 姜伯洋 wrote:
Thank you first!
My environment is a pdns master node, two pdns slave nodes, that is, three
servers. Whether I deploy on two slave nodes or all nodes deploy recursor,
master-slave synchronization fails!
From the node's configuration file:
Setgid=pdns
Setuid
On 11/03/2019 11:15, 姜伯洋 wrote:
Thank you first!
My environment is a pdns master node, two pdns slave nodes, that is, three
servers. Whether I deploy on two slave nodes or all nodes deploy recursor,
master-slave synchronization fails!
From the node's configuration file:
Setgid=pdns
Setuid
My backend is using mysql
This is my pdns configuration from the node:
setgid=pdns
setuid=pdns
daemon=yes
local-address=127.0.0.1
local-port=5300
loglevel=9
local-ipv6=
cache-ttl=60
negquery-cache-ttl=60
query-cache-ttl=60
receiver-threads=12
reuseport=yes
distributor-threads=20
launch=gmysql
gmy
At 2019-03-11 19:27:13, "Brian Candler" wrote:
Please reply to the list, not to me personally.
On 11/03/2019 11:15, 姜伯洋 wrote:
Thank you first!
My environment is a pdns master node, two pdns slave nodes, that is, three
servers. Whether I deploy on two slave nodes or all nodes deploy re
On 11/03/2019 08:49, 姜伯洋 wrote:
My system is centos7.4, the pdns version is 4.1, and the pdns-recursor
version is 4.1.
But when I changed the port of pdns to 5300, my master and slave nodes
could not be synchronized. It was ok before this.
Sorry, you need to be more specific.
You changed whic