SERVFAIL with unbound

yes Yes, the unbound is already running normally, and arm64 is only 1.6.7.

root@rockpi:~# sudo service unbound stop
root@rockpi:~# unbound -d -vvvv
[1552495417] unbound[341:0] notice: Start of unbound 1.6.7.
[1552495417] unbound[341:0] debug: increased limit(open files) from 1024 to 21558
[1552495417] unbound[341:0] debug: creating udp4 socket 127.0.0.1 5353
[1552495417] unbound[341:0] debug: creating tcp4 socket 127.0.0.1 5353
[1552495417] unbound[341:0] debug: creating udp4 socket 127.0.0.1 5353
[1552495417] unbound[341:0] debug: creating tcp4 socket 127.0.0.1 5353
[1552495417] unbound[341:0] debug: creating udp4 socket 127.0.0.1 5353
[1552495417] unbound[341:0] debug: creating tcp4 socket 127.0.0.1 5353
[1552495417] unbound[341:0] debug: creating udp4 socket 127.0.0.1 5353
[1552495417] unbound[341:0] debug: creating tcp4 socket 127.0.0.1 5353
[1552495417] unbound[341:0] debug: creating tcp4 socket 127.0.0.1 8953
[1552495417] unbound[341:0] debug: switching log to syslog

There is no latest ubound for armbian which is currently 1.6.7

root@rockpi:~# sudo service unbound stop
root@rockpi:~# unbound -d -vvvv
[1552496472] unbound[2880:0] notice: Start of unbound 1.6.7.
[1552496472] unbound[2880:0] debug: increased limit(open files) from 1024 to 21558
[1552496472] unbound[2880:0] debug: creating udp4 socket 127.0.0.1 5353
[1552496472] unbound[2880:0] debug: creating tcp4 socket 127.0.0.1 5353
[1552496472] unbound[2880:0] debug: creating udp4 socket 127.0.0.1 5353
[1552496472] unbound[2880:0] debug: creating tcp4 socket 127.0.0.1 5353
[1552496472] unbound[2880:0] debug: creating udp4 socket 127.0.0.1 5353
[1552496472] unbound[2880:0] debug: creating tcp4 socket 127.0.0.1 5353
[1552496472] unbound[2880:0] debug: creating udp4 socket 127.0.0.1 5353
[1552496472] unbound[2880:0] debug: creating tcp4 socket 127.0.0.1 5353
[1552496472] unbound[2880:0] debug: creating tcp4 socket 127.0.0.1 8953
[1552496472] unbound[2880:0] debug: switching log to syslog
root@rockpi:~# sudo service unbound start
root@rockpi:~#

Mar 14 01:08:29 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:29 dnsmasq[1182]: query[A] www.google.com.hk.lan from 192.168.1.149
Mar 14 01:08:29 dnsmasq[1182]: forwarded www.google.com.hk.lan to 192.168.1.1
Mar 14 01:08:30 dnsmasq[1182]: query[A] woodpecker.uc.cn from 192.168.1.149
Mar 14 01:08:30 dnsmasq[1182]: /etc/pihole/gravity.list woodpecker.uc.cn is NXDOMAIN
Mar 14 01:08:30 dnsmasq[1182]: query[A] woodpecker.uc.cn.lan from 192.168.1.149
Mar 14 01:08:30 dnsmasq[1182]: forwarded woodpecker.uc.cn.lan to 192.168.1.1
Mar 14 01:08:31 dnsmasq[1182]: query[A] www.google.com.hk.lan from 192.168.1.149
Mar 14 01:08:31 dnsmasq[1182]: forwarded www.google.com.hk.lan to 192.168.1.1
Mar 14 01:08:34 dnsmasq[1182]: query[A] www.google.com.hk from 192.168.1.149
Mar 14 01:08:34 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:34 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:34 dnsmasq[1182]: query[A] www.google.com.hk.lan from 192.168.1.149
Mar 14 01:08:34 dnsmasq[1182]: forwarded www.google.com.hk.lan to 192.168.1.1
Mar 14 01:08:35 dnsmasq[1182]: query[A] woodpecker.uc.cn.lan from 192.168.1.149
Mar 14 01:08:35 dnsmasq[1182]: forwarded woodpecker.uc.cn.lan to 192.168.1.1
Mar 14 01:08:36 dnsmasq[1182]: query[PTR] 0.1.168.192.in-addr.arpa from 192.168.1.1
Mar 14 01:08:37 dnsmasq[1182]: forwarded 0.1.168.192.in-addr.arpa to 192.168.1.1
Mar 14 01:08:39 dnsmasq[1182]: query[A] www.google.com.hk from 192.168.1.149
Mar 14 01:08:39 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:39 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:39 dnsmasq[1182]: query[A] www.google.com.hk.lan from 192.168.1.149
Mar 14 01:08:39 dnsmasq[1182]: forwarded www.google.com.hk.lan to 192.168.1.1
Mar 14 01:08:44 dnsmasq[1182]: query[A] www.google.com.hk from 192.168.1.149
Mar 14 01:08:44 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:44 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:44 dnsmasq[1182]: query[A] www.google.com.hk.lan from 192.168.1.149
Mar 14 01:08:44 dnsmasq[1182]: forwarded www.google.com.hk.lan to 192.168.1.1
Mar 14 01:08:44 dnsmasq[1182]: query[A] www.google.com.hk from 192.168.1.149
Mar 14 01:08:44 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:44 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:44 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:47 dnsmasq[1182]: query[PTR] 0.1.168.192.in-addr.arpa from 192.168.1.1
Mar 14 01:08:47 dnsmasq[1182]: forwarded 0.1.168.192.in-addr.arpa to 192.168.1.1
Mar 14 01:08:49 dnsmasq[1182]: query[A] www.google.com.hk from 192.168.1.149
Mar 14 01:08:49 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:49 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:49 dnsmasq[1182]: query[A] www.google.com.hk.lan from 192.168.1.149
Mar 14 01:08:49 dnsmasq[1182]: forwarded www.google.com.hk.lan to 192.168.1.1
Mar 14 01:08:49 dnsmasq[1182]: query[A] www.google.com.hk from 192.168.1.149
Mar 14 01:08:49 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1
Mar 14 01:08:49 dnsmasq[1182]: forwarded www.google.com.hk to 127.0.0.1

Always querying ip

Dnscryptproxy2.0 can parse www.googke.com.hk normally, but unbound can't! I plan to use dnscryptproxy

Unbound can't parse www.google.com.hk normally and Dnscryptproxy2.0 can be normal

Mar 14 01:15:50 dnsmasq[1313]: query[A] www.google.com.hk from 192.168.1.1
Mar 14 01:15:50 dnsmasq[1313]: cached www.google.com.hk is 172.217.11.163
Mar 14 01:15:50 dnsmasq[1313]: query[AAAA] www.google.com.hk from 192.168.1.1
Mar 14 01:15:50 dnsmasq[1313]: cached www.google.com.hk is 2404:6800:4004:80a::2003
Mar 14 01:16:14 dnsmasq[1313]: query[A] www.google.com.hk from 192.168.1.1
Mar 14 01:16:14 dnsmasq[1313]: cached www.google.com.hk is 172.217.11.163
Mar 14 01:16:14 dnsmasq[1313]: query[AAAA] www.google.com.hk from 192.168.1.1
Mar 14 01:16:14 dnsmasq[1313]: cached www.google.com.hk is 2404:6800:4004:80a::2003
Mar 14 01:16:44 dnsmasq[1313]: query[PTR] 0.1.168.192.in-addr.arpa from 192.168.1.1
Mar 14 01:16:44 dnsmasq[1313]: forwarded 0.1.168.192.in-addr.arpa to 192.168.1.1
Mar 14 01:16:47 dnsmasq[1313]: query[A] www.google.com.hk from 192.168.1.1

Dig can be parsed normally, but it is not possible to use unbound for recursion in pi hole, which is very strange.

i do not have DNSSEC enabled in Pi-hole

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.