![](https://secure.gravatar.com/avatar/78899cc7c86faadf459406c955cdae5e.jpg?s=120&d=mm&r=g)
Und das sieht doch eigentlich ganz ok aus, oder?
$ sudo unbound-control list_stubs . IN stub prime M.ROOT-SERVERS.NET. L.ROOT-SERVERS.NET. K.ROOT-SERVERS.NET. J.ROOT-SERVERS.NET. I.ROOT-SERVERS.NET. H.ROOT-SERVERS.NET. G.ROOT-SERVERS.NET. F.ROOT-SERVERS.NET. E.ROOT-SERVERS.NET. D.ROOT-SERVERS.NET. C.ROOT-SERVERS.NET. B.ROOT-SERVERS.NET. A.ROOT-SERVERS.NET. 2001:dc3::35 202.12.27.33 2001:500:9f::42 199.7.83.42 2001:7fd::1 193.0.14.129 2001:503:c27::2:30 192.58.128.30 2001:7fe::53 192.36.148.17 2001:500:1::53 198.97.190.53 2001:500:12::d0d 192.112.36.4 2001:500:2f::f 192.5.5.241 2001:500:a8::e 192.203.230.10 2001:500:2d::d 199.7.91.13 2001:500:2::c 192.33.4.12 2001:500:200::b 199.9.14.201 2001:503:ba3e::2:30 198.41.0.4 fritz.box. IN stub prime +i 192.168.178.1 178.168.192.in-addr.arpa. IN stub noprime 192.168.178.1
Am 2021-05-27 17:55, schrieb J. Fahrner:
Am 2021-05-27 17:47, schrieb J. Fahrner:
$ host 192.168.178.52 Host 52.178.168.192.in-addr.arpa not found: 2(SERVFAIL)
Kann damit jemand was anfangen?
$ dig @127.0.0.1 -p 5353 -x 192.168.178.52
; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> @127.0.0.1 -p 5353 -x 192.168.178.52 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13917 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;52.178.168.192.in-addr.arpa. IN PTR
;; AUTHORITY SECTION: 168.192.in-addr.arpa. 10800 IN SOA localhost. nobody.invalid. 1 3600 1200 604800 10800
;; Query time: 0 msec ;; SERVER: 127.0.0.1#5353(127.0.0.1) ;; WHEN: Do Mai 27 17:52:45 CEST 2021 ;; MSG SIZE rcvd: 115