我正在运行自己的 BIND9 服务器，该服务器在本地网络中的 Arch Linux 上运行。自从运行该服务器以来，我开始在浏览器中收到各种错误（Android 6 上的 Chrome）。这些错误通常会同时连续出现：
- DNS 探测错误
- 错误名称未解决
- err_timed_out（更新四）
只需单击错误消息并尝试重新加载页面，大约 30 秒后问题就会自行解决。我的日志没有显示任何可疑条目（journalctl -r -u named）。我发布了我的 bind9 配置以及下面的相关/正在运行的区域。是否有人可以指出任何明显的问题？我很乐意根据需要生成更多配置/日志文件或运行任何测试。我可能还应该提到我在同一台机器上设置了一个 dhcp 服务器。此外，该框还在带有 qemu 虚拟机管理程序的 kvm 中使用 libvirt 托管 windows server 2016 客户机。我在下面附上了ˋip addr showˋ 的输出。
更新一：再次检查我的 DNS 服务器日志后，发现确实有许多失败的查询。现在正在分析。日志附在最底部。感谢任何指点。谢谢！（我不是系统管理员，也不是软件开发人员，所以这真的不是我的专业领域）
更新二：通过明确设置要监听的地址可能解决了我的问题。在本例中：（listen-on { 192.168.1.35; };在/etc/named.conf）。将监控日志并最终在接下来的 24 小时内确认。
更新三：我的 dns 服务器日志中仍然收到servfail错误，但自从明确设置要监听的 ip 地址以来，我还没有收到此设备上的浏览器中的任何错误，而且我也觉得查询性能有所提高。后者当然是非常主观的。错误servfail指向query.c第 8298 行的 C 文件。我还在研究edns-udp-size与我的路由器/互联网调制解调器相关的 bind9 参数。我曾经将 Telekom Speedport W920V 刷入 AVM FritzBox 7570 vDSL，我仍然将其用作我的 vDSL 调制解调器/路由器。仍然非常希望得到一些指点。干杯。
更新四：如上所述添加了额外的浏览器错误。此外，正如 UIII 中提到的，我正在EDNS-UDP-SIZE根据以下日志条目查看该参数：
Feb 07 19:05:01 nas named[10928]: success resolving 'clients4.google.com/A' (in '.'?) after reducing the advertised EDNS UDP packet size to 512 octets
Feb 07 19:04:54 nas named[10928]: client @0x7f7a18204640 192.168.1.31#14927 (clients4.google.com): query: clients4.google.com IN A + (192.168.1.35)
ip addr show 的输出：
$ ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UP group default qlen 1000
link/ether e0:cb:4e:42:ee:e3 brd ff:ff:ff:ff:ff:ff
inet6 fe80::8259:5b3a:8510:f42/64 scope link
valid_lft forever preferred_lft forever
3: enp6s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 68:05:ca:4a:82:b1 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.33/24 brd 192.168.1.255 scope global enp6s0
valid_lft forever preferred_lft forever
inet6 fe80::510b:e84e:e0ec:5736/64 scope link
valid_lft forever preferred_lft forever
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 52:d4:72:9d:eb:d7 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.35/24 brd 192.168.1.255 scope global br0
valid_lft forever preferred_lft forever
inet 192.168.1.115/24 brd 192.168.1.255 scope global secondary br0
valid_lft forever preferred_lft forever
inet6 fe80::a9ed:5871:8928:e54c/64 scope link
valid_lft forever preferred_lft forever
inet6 fe80::50d4:72ff:fe9d:ebd7/64 scope link
valid_lft forever preferred_lft forever
5: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:4c:bf:cc brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
6: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000
link/ether 52:54:00:4c:bf:cc brd ff:ff:ff:ff:ff:ff
9: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br0 state UNKNOWN group default qlen 1000
link/ether fe:54:00:78:91:29 brd ff:ff:ff:ff:ff:ff
inet6 fe80::18cc:6a42:e2b9:6fe4/64 scope link
valid_lft forever preferred_lft forever
这是我的 bind9 配置：
acl allowedclients {
192.168.1.0/24;
localhost;
127.0.0.1;
};
options {
directory "/var/named";
pid-file "/run/named/named.pid";
recursion yes;
allow-recursion { 192.168.1.0/24; 127.0.0.1; };
allow-query { allowedclients; };
forwarders {
8.8.8.8;
8.8.4.4;
};
forward only;
dnssec-enable yes;
dnssec-validation yes;
auth-nxdomain no; # conform to RFC1035
listen-on-v6 { any; };
listen-on port 53 { any; };
};
# Use with the following in named.conf, adjusting the allow list as needed:
include "/etc/rndc.key";
#
controls {
inet 127.0.0.1 port 8222
allow { 127.0.0.1; } keys { "rndc-key"; };
};
zone "localhost" in {
type master;
file "/var/named/localhost.zone";
};
zone "0.0.127.in-addr.arpa" in {
type master;
file "/var/named/127.0.0.zone";
};
zone "muncic.local" in {
type master;
file "/var/named/muncic.local.zone";
};
zone "1.168.192.in-addr.arpa" in {
type master;
notify no;
file "/var/named/192.168.1.zone";
};
这是我的前锋区域：
$TTL 3D ; default ttl for records without a specified lifetime
;$ORIGIN muncic.local.
@ IN SOA nas.muncic.local. root.muncic.local. (
2017020201 ; serial number
16384 ; ns refresh
2048 ; ns retry
1048576 ; authority expiry
2560 ); min (RFC2308 ยง4)
muncic.local. IN NS nas.muncic.local.
IN NS google-public-dns-a.google.com.
;nas IN MX 192.168.1.35
muncic.local. IN A 192.168.1.35
nas IN A 192.168.1.35
a.mx IN A 192.168.1.35
0.0.1.168.192 IN A 192.168.1.0
router IN A 192.168.1.1
2.0.1.168.192 IN A 192.168.1.2
3.0.1.168.192 IN A 192.168.1.3
4.0.1.168.192 IN A 192.168.1.4
5.0.1.168.192 IN A 192.168.1.5
6.0.1.168.192 IN A 192.168.1.6
7.0.1.168.192 IN A 192.168.1.7
8.0.1.168.192 IN A 192.168.1.8
9.0.1.168.192 IN A 192.168.1.9
s7e IN A 192.168.1.10
11.0.1.168.192 IN A 192.168.1.11
winsrv16 IN A 192.168.1.12
13.0.1.168.192 IN A 192.168.1.13
14.0.1.168.192 IN A 192.168.1.14
15.0.1.168.192 IN A 192.168.1.15
16.0.1.168.192 IN A 192.168.1.16
17.0.1.168.192 IN A 192.168.1.17
18.0.1.168.192 IN A 192.168.1.18
19.0.1.168.192 IN A 192.168.1.19
20.0.1.168.192 IN A 192.168.1.20
21.0.1.168.192 IN A 192.168.1.21
22.0.1.168.192 IN A 192.168.1.22
23.0.1.168.192 IN A 192.168.1.23
htpc IN A 192.168.1.24
main IN A 192.168.1.25
26.0.1.168.192 IN A 192.168.1.26
27.0.1.168.192 IN A 192.168.1.27
28.0.1.168.192 IN A 192.168.1.28
29.0.1.168.192 IN A 192.168.1.29
30.0.1.168.192 IN A 192.168.1.30
s2 IN A 192.168.1.31
32.0.1.168.192 IN A 192.168.1.32
33.0.1.168.192 IN A 192.168.1.33
34.0.1.168.192 IN A 192.168.1.34
nas IN A 192.168.1.35
36.0.1.168.192 IN A 192.168.1.36
37.0.1.168.192 IN A 192.168.1.37
38.0.1.168.192 IN A 192.168.1.38
39.0.1.168.192 IN A 192.168.1.39
40.0.1.168.192 IN A 192.168.1.40
41.0.1.168.192 IN A 192.168.1.41
42.0.1.168.192 IN A 192.168.1.42
43.0.1.168.192 IN A 192.168.1.43
44.0.1.168.192 IN A 192.168.1.44
45.0.1.168.192 IN A 192.168.1.45
46.0.1.168.192 IN A 192.168.1.46
47.0.1.168.192 IN A 192.168.1.47
48.0.1.168.192 IN A 192.168.1.48
49.0.1.168.192 IN A 192.168.1.49
50.0.1.168.192 IN A 192.168.1.50
51.0.1.168.192 IN A 192.168.1.51
52.0.1.168.192 IN A 192.168.1.52
53.0.1.168.192 IN A 192.168.1.53
54.0.1.168.192 IN A 192.168.1.54
55.0.1.168.192 IN A 192.168.1.55
56.0.1.168.192 IN A 192.168.1.56
57.0.1.168.192 IN A 192.168.1.57
58.0.1.168.192 IN A 192.168.1.58
59.0.1.168.192 IN A 192.168.1.59
60.0.1.168.192 IN A 192.168.1.60
61.0.1.168.192 IN A 192.168.1.61
62.0.1.168.192 IN A 192.168.1.62
63.0.1.168.192 IN A 192.168.1.63
64.0.1.168.192 IN A 192.168.1.64
65.0.1.168.192 IN A 192.168.1.65
66.0.1.168.192 IN A 192.168.1.66
67.0.1.168.192 IN A 192.168.1.67
68.0.1.168.192 IN A 192.168.1.68
69.0.1.168.192 IN A 192.168.1.69
70.0.1.168.192 IN A 192.168.1.70
71.0.1.168.192 IN A 192.168.1.71
72.0.1.168.192 IN A 192.168.1.72
73.0.1.168.192 IN A 192.168.1.73
74.0.1.168.192 IN A 192.168.1.74
75.0.1.168.192 IN A 192.168.1.75
76.0.1.168.192 IN A 192.168.1.76
77.0.1.168.192 IN A 192.168.1.77
78.0.1.168.192 IN A 192.168.1.78
79.0.1.168.192 IN A 192.168.1.79
80.0.1.168.192 IN A 192.168.1.80
81.0.1.168.192 IN A 192.168.1.81
82.0.1.168.192 IN A 192.168.1.82
83.0.1.168.192 IN A 192.168.1.83
84.0.1.168.192 IN A 192.168.1.84
85.0.1.168.192 IN A 192.168.1.85
86.0.1.168.192 IN A 192.168.1.86
87.0.1.168.192 IN A 192.168.1.87
88.0.1.168.192 IN A 192.168.1.88
89.0.1.168.192 IN A 192.168.1.89
90.0.1.168.192 IN A 192.168.1.90
91.0.1.168.192 IN A 192.168.1.91
92.0.1.168.192 IN A 192.168.1.92
93.0.1.168.192 IN A 192.168.1.93
94.0.1.168.192 IN A 192.168.1.94
95.0.1.168.192 IN A 192.168.1.95
96.0.1.168.192 IN A 192.168.1.96
97.0.1.168.192 IN A 192.168.1.97
98.0.1.168.192 IN A 192.168.1.98
99.0.1.168.192 IN A 192.168.1.99
100.0.1.168.192 IN A 192.168.1.100
101.0.1.168.192 IN A 192.168.1.101
102.0.1.168.192 IN A 192.168.1.102
103.0.1.168.192 IN A 192.168.1.103
104.0.1.168.192 IN A 192.168.1.104
105.0.1.168.192 IN A 192.168.1.105
106.0.1.168.192 IN A 192.168.1.106
107.0.1.168.192 IN A 192.168.1.107
108.0.1.168.192 IN A 192.168.1.108
109.0.1.168.192 IN A 192.168.1.109
110.0.1.168.192 IN A 192.168.1.110
111.0.1.168.192 IN A 192.168.1.111
112.0.1.168.192 IN A 192.168.1.112
113.0.1.168.192 IN A 192.168.1.113
114.0.1.168.192 IN A 192.168.1.114
115.0.1.168.192 IN A 192.168.1.115
116.0.1.168.192 IN A 192.168.1.116
117.0.1.168.192 IN A 192.168.1.117
118.0.1.168.192 IN A 192.168.1.118
119.0.1.168.192 IN A 192.168.1.119
120.0.1.168.192 IN A 192.168.1.120
121.0.1.168.192 IN A 192.168.1.121
122.0.1.168.192 IN A 192.168.1.122
123.0.1.168.192 IN A 192.168.1.123
124.0.1.168.192 IN A 192.168.1.124
125.0.1.168.192 IN A 192.168.1.125
126.0.1.168.192 IN A 192.168.1.126
127.0.1.168.192 IN A 192.168.1.127
t813n IN CNAME s2.muncic.local.
g935f IN CNAME s7e.muncic.local.
jira IN CNAME winsrv16.muncic.local.
www IN CNAME muncic.local.
这是我的反向区域：
$TTL 3D ; default ttl for records without a specified lifetime
;$ORIGIN 0.1.168.192.in-addr.arpa.
@ IN SOA nas.muncic.local. root.muncic.local. (
2017020201 ; serial number
16384 ; ns refresh
2048 ; ns retry
1048576 ; authority expiry
2560 ); min (RFC2308 ยง4)
IN NS nas.muncic.local.
IN NS google-public-dns-a.google.com.
35 IN PTR a.mx.muncic.local.
0 IN PTR 0.0.1.168.192.muncic.local.
1 IN PTR router
2 IN PTR 2.0.1.168.192.muncic.local.
3 IN PTR 3.0.1.168.192.muncic.local.
4 IN PTR 4.0.1.168.192.muncic.local.
5 IN PTR 5.0.1.168.192.muncic.local.
6 IN PTR 6.0.1.168.192.muncic.local.
7 IN PTR 7.0.1.168.192.muncic.local.
8 IN PTR 8.0.1.168.192.muncic.local.
9 IN PTR 9.0.1.168.192.muncic.local.
10 IN PTR s7e
11 IN PTR 11.0.1.168.192.muncic.local.
12 IN PTR winsrv16
13 IN PTR 13.0.1.168.192.muncic.local.
14 IN PTR 14.0.1.168.192.muncic.local.
15 IN PTR 15.0.1.168.192.muncic.local.
16 IN PTR 16.0.1.168.192.muncic.local.
17 IN PTR 17.0.1.168.192.muncic.local.
18 IN PTR 18.0.1.168.192.muncic.local.
19 IN PTR 19.0.1.168.192.muncic.local.
20 IN PTR 20.0.1.168.192.muncic.local.
21 IN PTR 21.0.1.168.192.muncic.local.
22 IN PTR 22.0.1.168.192.muncic.local.
23 IN PTR 23.0.1.168.192.muncic.local.
24 IN PTR htpc
25 IN PTR main
26 IN PTR 26.0.1.168.192.muncic.local.
27 IN PTR 27.0.1.168.192.muncic.local.
28 IN PTR 28.0.1.168.192.muncic.local.
29 IN PTR 29.0.1.168.192.muncic.local.
30 IN PTR 30.0.1.168.192.muncic.local.
31 IN PTR s2
32 IN PTR 32.0.1.168.192.muncic.local.
33 IN PTR 33.0.1.168.192.muncic.local.
34 IN PTR 34.0.1.168.192.muncic.local.
35 IN PTR 35.0.1.168.192.muncic.local.
36 IN PTR 36.0.1.168.192.muncic.local.
37 IN PTR 37.0.1.168.192.muncic.local.
38 IN PTR 38.0.1.168.192.muncic.local.
39 IN PTR 39.0.1.168.192.muncic.local.
40 IN PTR 40.0.1.168.192.muncic.local.
41 IN PTR 41.0.1.168.192.muncic.local.
42 IN PTR 42.0.1.168.192.muncic.local.
43 IN PTR 43.0.1.168.192.muncic.local.
44 IN PTR 44.0.1.168.192.muncic.local.
45 IN PTR 45.0.1.168.192.muncic.local.
46 IN PTR 46.0.1.168.192.muncic.local.
47 IN PTR 47.0.1.168.192.muncic.local.
48 IN PTR 48.0.1.168.192.muncic.local.
49 IN PTR 49.0.1.168.192.muncic.local.
50 IN PTR 50.0.1.168.192.muncic.local.
51 IN PTR 51.0.1.168.192.muncic.local.
52 IN PTR 52.0.1.168.192.muncic.local.
53 IN PTR 53.0.1.168.192.muncic.local.
54 IN PTR 54.0.1.168.192.muncic.local.
55 IN PTR 55.0.1.168.192.muncic.local.
56 IN PTR 56.0.1.168.192.muncic.local.
57 IN PTR 57.0.1.168.192.muncic.local.
58 IN PTR 58.0.1.168.192.muncic.local.
59 IN PTR 59.0.1.168.192.muncic.local.
60 IN PTR 60.0.1.168.192.muncic.local.
61 IN PTR 61.0.1.168.192.muncic.local.
62 IN PTR 62.0.1.168.192.muncic.local.
63 IN PTR 63.0.1.168.192.muncic.local.
64 IN PTR 64.0.1.168.192.muncic.local.
65 IN PTR 65.0.1.168.192.muncic.local.
66 IN PTR 66.0.1.168.192.muncic.local.
67 IN PTR 67.0.1.168.192.muncic.local.
68 IN PTR 68.0.1.168.192.muncic.local.
69 IN PTR 69.0.1.168.192.muncic.local.
70 IN PTR 70.0.1.168.192.muncic.local.
71 IN PTR 71.0.1.168.192.muncic.local.
72 IN PTR 72.0.1.168.192.muncic.local.
73 IN PTR 73.0.1.168.192.muncic.local.
74 IN PTR 74.0.1.168.192.muncic.local.
75 IN PTR 75.0.1.168.192.muncic.local.
76 IN PTR 76.0.1.168.192.muncic.local.
77 IN PTR 77.0.1.168.192.muncic.local.
78 IN PTR 78.0.1.168.192.muncic.local.
79 IN PTR 79.0.1.168.192.muncic.local.
80 IN PTR 80.0.1.168.192.muncic.local.
81 IN PTR 81.0.1.168.192.muncic.local.
82 IN PTR 82.0.1.168.192.muncic.local.
83 IN PTR 83.0.1.168.192.muncic.local.
84 IN PTR 84.0.1.168.192.muncic.local.
85 IN PTR 85.0.1.168.192.muncic.local.
86 IN PTR 86.0.1.168.192.muncic.local.
87 IN PTR 87.0.1.168.192.muncic.local.
88 IN PTR 88.0.1.168.192.muncic.local.
89 IN PTR 89.0.1.168.192.muncic.local.
90 IN PTR 90.0.1.168.192.muncic.local.
91 IN PTR 91.0.1.168.192.muncic.local.
92 IN PTR 92.0.1.168.192.muncic.local.
93 IN PTR 93.0.1.168.192.muncic.local.
94 IN PTR 94.0.1.168.192.muncic.local.
95 IN PTR 95.0.1.168.192.muncic.local.
96 IN PTR 96.0.1.168.192.muncic.local.
97 IN PTR 97.0.1.168.192.muncic.local.
98 IN PTR 98.0.1.168.192.muncic.local.
99 IN PTR 99.0.1.168.192.muncic.local.
100 IN PTR 100.0.1.168.192.muncic.local.
101 IN PTR 101.0.1.168.192.muncic.local.
102 IN PTR 102.0.1.168.192.muncic.local.
103 IN PTR 103.0.1.168.192.muncic.local.
104 IN PTR 104.0.1.168.192.muncic.local.
105 IN PTR 105.0.1.168.192.muncic.local.
106 IN PTR 106.0.1.168.192.muncic.local.
107 IN PTR 107.0.1.168.192.muncic.local.
108 IN PTR 108.0.1.168.192.muncic.local.
109 IN PTR 109.0.1.168.192.muncic.local.
110 IN PTR 110.0.1.168.192.muncic.local.
111 IN PTR 111.0.1.168.192.muncic.local.
112 IN PTR 112.0.1.168.192.muncic.local.
113 IN PTR 113.0.1.168.192.muncic.local.
114 IN PTR 114.0.1.168.192.muncic.local.
115 IN PTR 115.0.1.168.192.muncic.local.
116 IN PTR 116.0.1.168.192.muncic.local.
117 IN PTR 117.0.1.168.192.muncic.local.
118 IN PTR 118.0.1.168.192.muncic.local.
119 IN PTR 119.0.1.168.192.muncic.local.
120 IN PTR 120.0.1.168.192.muncic.local.
121 IN PTR 121.0.1.168.192.muncic.local.
122 IN PTR 122.0.1.168.192.muncic.local.
123 IN PTR 123.0.1.168.192.muncic.local.
124 IN PTR 124.0.1.168.192.muncic.local.
125 IN PTR 125.0.1.168.192.muncic.local.
126 IN PTR 126.0.1.168.192.muncic.local.
127 IN PTR 127.0.1.168.192.muncic.local.
journalctl 的输出如下（完整日志)：
$ journalctl -r -u named --since="2017-02-06 21:23:20" | grep 192.168.1.31
Feb 06 21:23:53 nas named[13865]: client @0x7f2a5419f1c0 192.168.1.31#12998 (www.jspell.com): query: www.jspell.com IN A + (192.168.1.35)
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38024500 192.168.1.31#12998 (www.jspell.com): query: www.jspell.com IN A + (192.168.1.35)
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38024500 192.168.1.31#1803 (www.gstatic.com.muncic.local): query: www.gstatic.com.muncic.local IN A + (192.168.1.35)
Feb 06 21:23:48 nas named[13865]: client @0x7f2a4400de10 192.168.1.31#5616 (www.gstatic.com): query failed (SERVFAIL) for www.gstatic.com/IN/A at query.c:6805
Feb 06 21:23:48 nas named[13865]: client @0x7f2a4400de10 192.168.1.31#5616 (www.gstatic.com): query: www.gstatic.com IN A + (192.168.1.35)
Feb 06 21:23:48 nas named[13865]: client @0x7f2a3c10fd90 192.168.1.31#22885 (www.gstatic.com): query failed (SERVFAIL) for www.gstatic.com/IN/A at query.c:8298
Feb 06 21:23:48 nas named[13865]: client @0x7f2a54d09360 192.168.1.31#9720 (www.gstatic.com): query failed (SERVFAIL) for www.gstatic.com/IN/A at query.c:8298
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38024500 192.168.1.31#9195 (cdnjs.cloudflare.com): query failed (SERVFAIL) for cdnjs.cloudflare.com/IN/A at query.c:6805
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38024500 192.168.1.31#9195 (cdnjs.cloudflare.com): query: cdnjs.cloudflare.com IN A + (192.168.1.35)
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38024500 192.168.1.31#15094 (cdnjs.cloudflare.com): query failed (SERVFAIL) for cdnjs.cloudflare.com/IN/A at query.c:6805
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38024500 192.168.1.31#15094 (cdnjs.cloudflare.com): query: cdnjs.cloudflare.com IN A + (192.168.1.35)
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38024500 192.168.1.31#11314 (www.google.de): query failed (SERVFAIL) for www.google.de/IN/A at query.c:6805
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38024500 192.168.1.31#11314 (www.google.de): query: www.google.de IN A + (192.168.1.35)
Feb 06 21:23:48 nas named[13865]: client @0x7f2a54173d80 192.168.1.31#26564 (cdnjs.cloudflare.com): query failed (SERVFAIL) for cdnjs.cloudflare.com/IN/A at query.c:8298
Feb 06 21:23:48 nas named[13865]: client @0x7f2a40013ed0 192.168.1.31#29727 (www.google.de): query failed (SERVFAIL) for www.google.de/IN/A at query.c:8298
Feb 06 21:23:48 nas named[13865]: client @0x7f2a54da5e20 192.168.1.31#28030 (www.google.de): query failed (SERVFAIL) for www.google.de/IN/A at query.c:8298
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38024500 192.168.1.31#31811 (azurecomcdn.azureedge.net): query failed (SERVFAIL) for azurecomcdn.azureedge.net/IN/A at query.c:6805
Feb 06 21:23:48 nas named[13865]: client @0x7f2a54a3f1b0 192.168.1.31#15173 (maxcdn.bootstrapcdn.com): query failed (SERVFAIL) for maxcdn.bootstrapcdn.com/IN/A at query.c:6805
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38024500 192.168.1.31#31811 (azurecomcdn.azureedge.net): query: azurecomcdn.azureedge.net IN A + (192.168.1.35)
Feb 06 21:23:48 nas named[13865]: client @0x7f2a54a3f1b0 192.168.1.31#15173 (maxcdn.bootstrapcdn.com): query: maxcdn.bootstrapcdn.com IN A + (192.168.1.35)
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38023a80 192.168.1.31#28154 (id.google.de): query: id.google.de IN A + (192.168.1.35)
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38023a80 192.168.1.31#25790 (maxcdn.bootstrapcdn.com): query failed (SERVFAIL) for maxcdn.bootstrapcdn.com/IN/A at query.c:6805
Feb 06 21:23:48 nas named[13865]: client @0x7f2a3c019270 192.168.1.31#4902 (azurecomcdn.azureedge.net): query failed (SERVFAIL) for azurecomcdn.azureedge.net/IN/A at query.c:6805
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38023a80 192.168.1.31#25790 (maxcdn.bootstrapcdn.com): query: maxcdn.bootstrapcdn.com IN A + (192.168.1.35)
Feb 06 21:23:48 nas named[13865]: client @0x7f2a3c019270 192.168.1.31#4902 (azurecomcdn.azureedge.net): query: azurecomcdn.azureedge.net IN A + (192.168.1.35)
Feb 06 21:23:48 nas named[13865]: client @0x7f2a38011920 192.168.1.31#5589 (maxcdn.bootstrapcdn.com): query failed (SERVFAIL) for maxcdn.bootstrapcdn.com/IN/A at query.c:8298
Feb 06 21:23:48 nas named[13865]: client @0x7f2a4c032bd0 192.168.1.31#24651 (id.google.de): query failed (SERVFAIL) for id.google.de/IN/A at query.c:8298
Feb 06 21:23:48 nas named[13865]: client @0x7f2a4c00bb60 192.168.1.31#12649 (id.google.de): query failed (SERVFAIL) for id.google.de/IN/A at query.c:8298
Feb 06 21:23:48 nas named[13865]: client @0x7f2a54d578c0 192.168.1.31#10242 (azurecomcdn.azureedge.net): query failed (SERVFAIL) for azurecomcdn.azureedge.net/IN/A at query.c:8298
Feb 06 21:23:44 nas named[13865]: client @0x7f2a3c10fd90 192.168.1.31#22885 (www.gstatic.com): query: www.gstatic.com IN A + (192.168.1.35)
Feb 06 21:23:44 nas named[13865]: client @0x7f2a54da5e20 192.168.1.31#28030 (www.google.de): query: www.google.de IN A + (192.168.1.35)
答案1
问题已经得到解决。我创建了一个github 仓库我在其中添加了所有相关的命名配置文件以及日志，以便比较命名服务器的损坏配置版本和正常工作配置版本。最终我无法真正确定问题所在，但可能是我的正向和反向区域配置错误。在我的正向区域中，声明 NS 记录时，我添加了域，如下所示
muncic.local. NS IN nas.muncic.local.
代替
NS IN nas.muncic.local.
在我的反向区域中，我发现一条 PTR 记录未使用正确的值
35 IN PTR 35.0.1.168.192.muncic.local.
代替
35 IN PTR nas
我还对我的 named.conf 绑定进行了各种更改，将其命名为在 192.168.1.33 上运行的第二个有线接口 enp6s0。
这是我在修复前后分别大约 24 小时的 journalctl 输出：
$ journalctl -u named --since="2017-02-12" --until="2017-02-13" | grep SERVFAIL -c
67
$ journalctl -u named --since="2017-02-14" | grep SERVFAIL -c
0