[Pdns-users] Analysis sometimes succeeds sometimes unsuccessful

[姜伯洋]

Now that there is no failure to resolve, all are in a successful state, but I have not done anything, but after a period of time to resolve, it becomes a success.
forward-zones-recurse=.=223.4.4.4


223.4.4.4 is just a public dns server address, when the client does not resolve my private area, I turn it here


10.3.9.140 Running my authoritative server node

[root at ops-dns-authoritative-1 ~]# ip a|grep eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    inet 10.3.9.140/24 brd 10.3.9.255 scope global eth0
[root at ops-dns-authoritative-1 ~]# rpm -qa |grep pdns
pdns-backend-mysql-4.1.10-1.el7.x86_64
pdns-4.1.10-1.el7.x86_64



在 2019-08-22 16:24:43，"Brian Candler" <b.candler at pobox.com> 写道：

On 22/08/2019 09:16, 姜伯洋 wrote:

The following is the configuration file of the recursive node


cat recursor.conf
local-address=10.3.9.100
local-port=53
forward-zones=test.com=10.3.9.140:5300
forward-zones-recurse=.=223.4.




What are you trying to do with "forward-zones-recurse"?   Have you just missed out parts of the IP address?


If you do "dig +norec @10.3.9.140 user.test.com" ten times, what results do you get?

What DNS software is 10.3.9.140 running?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20190822/a6b1b2dd/attachment.html>