Stimmt. Es müsste sich dabei, wenn ich es richtig verstehe, um die Anfragen vom Router (bzw. von anderen Geräten durch den Router) ans pi-hole handeln.
Nicht, dass ich wüsste - alles wurde so eingerichtet wie in der Anleitung oben beschrieben. Wie kann ich das prüfen?
Ich weiß nicht, wie ich nachverfolgen kann, welcher Client welche Anfragen stellt. Hast du eine gute Idee? Bisher ist mir keiner bekannt.
Das scheint an sich zu funktionieren.
Gerade konnte ich nicht mehr auf diese Foren-Website zugreifen.
Das unbound-log zeigte mir (grep -n -A3 "pi-hole.net" /var/log/unbound/unbound.log | tail -n 100
):
1038193-Aug 09 14:47:17 unbound[644:0] info: reply from <net.> 192.26.92.30#53
1038194-Aug 09 14:47:17 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038195-Aug 09 14:47:17 unbound[644:0] info: mark as REC_LAME
1038196:Aug 09 14:47:17 unbound[644:0] info: response for pi-hole.net. DS IN
1038197-Aug 09 14:47:17 unbound[644:0] info: reply from <net.> 192.31.80.30#53
1038198-Aug 09 14:47:17 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038199-Aug 09 14:47:17 unbound[644:0] info: mark as REC_LAME
1038200:Aug 09 14:47:17 unbound[644:0] info: response for pi-hole.net. DS IN
1038201-Aug 09 14:47:17 unbound[644:0] info: reply from <net.> 192.12.94.30#53
1038202-Aug 09 14:47:17 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038203-Aug 09 14:47:17 unbound[644:0] info: mark as REC_LAME
1038204:Aug 09 14:47:17 unbound[644:0] info: response for pi-hole.net. DS IN
1038205-Aug 09 14:47:17 unbound[644:0] info: reply from <net.> 192.54.112.30#53
1038206-Aug 09 14:47:17 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038207-Aug 09 14:47:17 unbound[644:0] info: mark as REC_LAME
1038208:Aug 09 14:47:17 unbound[644:0] info: response for pi-hole.net. DS IN
1038209-Aug 09 14:47:17 unbound[644:0] info: reply from <net.> 192.31.80.30#53
1038210-Aug 09 14:47:17 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038211-Aug 09 14:47:17 unbound[644:0] info: mark as REC_LAME
1038212:Aug 09 14:47:17 unbound[644:0] info: response for pi-hole.net. DS IN
1038213-Aug 09 14:47:17 unbound[644:0] info: reply from <net.> 192.52.178.30#53
1038214-Aug 09 14:47:17 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038215-Aug 09 14:47:17 unbound[644:0] info: mark as REC_LAME
1038216:Aug 09 14:47:17 unbound[644:0] info: response for pi-hole.net. DS IN
1038217-Aug 09 14:47:17 unbound[644:0] info: reply from <net.> 192.12.94.30#53
1038218-Aug 09 14:47:17 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038219-Aug 09 14:47:17 unbound[644:0] info: mark as REC_LAME
1038220:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038221-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.12.94.30#53
1038222-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038223-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038224:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038225-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.31.80.30#53
1038226-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038227-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038228:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038229-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.26.92.30#53
1038230-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038231-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038232:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038233-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.31.80.30#53
1038234-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038235-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038236:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038237-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.52.178.30#53
1038238-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038239-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038240:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038241-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.54.112.30#53
1038242-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038243-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038244:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038245-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.35.51.30#53
1038246-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038247-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038248:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038249-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.35.51.30#53
1038250-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038251-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038252:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038253-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.41.162.30#53
1038254-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038255-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038256:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038257-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.35.51.30#53
1038258-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038259-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038260:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038261-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.54.112.30#53
1038262-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038263-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038264:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038265-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.35.51.30#53
1038266-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038267-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038268:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038269-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.35.51.30#53
1038270-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038271-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038272:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038273-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.41.162.30#53
1038274-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038275-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038276:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038277-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.26.92.30#53
1038278-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038279-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038280:Aug 09 14:47:18 unbound[644:0] info: response for pi-hole.net. DS IN
1038281-Aug 09 14:47:18 unbound[644:0] info: reply from <net.> 192.41.162.30#53
1038282-Aug 09 14:47:18 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038283-Aug 09 14:47:18 unbound[644:0] info: mark as REC_LAME
1038284:Aug 09 14:47:19 unbound[644:0] info: response for pi-hole.net. DS IN
1038285-Aug 09 14:47:19 unbound[644:0] info: reply from <net.> 192.41.162.30#53
1038286-Aug 09 14:47:19 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
1038287-Aug 09 14:47:19 unbound[644:0] info: mark as REC_LAME
--
1038289:Aug 09 14:47:19 unbound[644:0] info: Could not establish a chain of trust to keys for pi-hole.net. DNSKEY IN
1038290-Aug 09 14:47:27 unbound[644:0] info: resolving www.apple.com. A IN
1038291-Aug 09 14:47:27 unbound[644:0] info: resolving www.apple.com. A IN
1038292-Aug 09 14:47:27 unbound[644:0] info: resolving www.apple.com. A IN
Mein Tomato-Router zeigte:
Aug 9 14:40:12 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:40:29 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:40:35 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:42:01 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:42:15 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:42:27 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:43:56 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:44:11 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:44:22 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:44:58 unknown daemon.info dnsmasq-dhcp[1210]: DHCPREQUEST(br0) 192.168.1.28 70:70:0d:75:6a:65
Aug 9 14:44:58 unknown daemon.info dnsmasq-dhcp[1210]: DHCPNAK(br0) 192.168.1.28 70:70:0d:75:6a:65 static lease available
Aug 9 14:44:58 unknown daemon.info dnsmasq-dhcp[1210]: DHCPREQUEST(br0) 192.168.1.28 70:70:0d:75:6a:65
Aug 9 14:44:58 unknown daemon.info dnsmasq-dhcp[1210]: DHCPNAK(br0) 192.168.1.28 70:70:0d:75:6a:65 static lease available
Aug 9 14:44:58 unknown daemon.info dnsmasq-dhcp[1210]: DHCPDISCOVER(br0) 70:70:0d:75:6a:65
Aug 9 14:44:58 unknown daemon.info dnsmasq-dhcp[1210]: DHCPOFFER(br0) 192.168.1.22 70:70:0d:75:6a:65
Aug 9 14:44:59 unknown daemon.info dnsmasq-dhcp[1210]: DHCPREQUEST(br0) 192.168.1.22 70:70:0d:75:6a:65
Aug 9 14:44:59 unknown daemon.info dnsmasq-dhcp[1210]: DHCPACK(br0) 192.168.1.22 70:70:0d:75:6a:65 XXXX
Aug 9 14:45:10 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:45:22 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:45:29 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:45:36 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:45:45 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:45:53 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:45:59 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:46:05 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:46:11 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:46:17 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:46:23 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:46:29 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:46:47 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:46:53 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:47:45 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:47:59 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:48:14 unknown daemon.warn dnsmasq[1210]: Maximum number of concurrent DNS queries reached (max: 150)
Aug 9 14:48:33 unknown daemon.info dnsmasq-dhcp[1210]: DHCPDISCOVER(br0) cc:3a:61:49:8c:a1
Aug 9 14:48:33 unknown daemon.info dnsmasq-dhcp[1210]: DHCPOFFER(br0) 192.168.1.21 cc:3a:61:49:8c:a1
Aug 9 14:48:33 unknown daemon.info dnsmasq-dhcp[1210]: DHCPREQUEST(br0) 192.168.1.21 cc:3a:61:49:8c:a1
Aug 9 14:48:33 unknown daemon.info dnsmasq-dhcp[1210]: DHCPACK(br0) 192.168.1.21 cc:3a:61:49:8c:a1 XXXX
Nach etwa 10 Minuten hatte sich das Problem wieder gelöst.
EDIT 1: Was sich allerdings nicht gelöst hat ist die Anfrage nach einem universitätsnahen Mail-Frontend (hier ersetzt durch 'secret-mailgui
'):
--
1020993:Aug 09 14:41:29 unbound[644:0] info: resolving mail.secret-mailgui.de. A IN
1020994:Aug 09 14:41:29 unbound[644:0] info: response for mail.secret-mailgui.de. A IN
1020995:Aug 09 14:41:29 unbound[644:0] info: reply from <secret-mailgui.de.> 129.143.2.10#53
1020996-Aug 09 14:41:29 unbound[644:0] info: query response was LAME
1020997:Aug 09 14:41:30 unbound[644:0] info: response for mail.secret-mailgui.de. A IN
1020998:Aug 09 14:41:30 unbound[644:0] info: reply from <secret-mailgui.de.> 193.196.199.1#53
1020999-Aug 09 14:41:30 unbound[644:0] info: query response was LAME
1021000:Aug 09 14:41:30 unbound[644:0] info: response for mail.secret-mailgui.de. A IN
1021001:Aug 09 14:41:30 unbound[644:0] info: reply from <secret-mailgui.de.> 129.143.253.133#53
1021002-Aug 09 14:41:30 unbound[644:0] info: query response was LAME
1021003-Aug 09 14:41:30 unbound[644:0] info: response for whatsapp.net. DS IN
1021004-Aug 09 14:41:30 unbound[644:0] info: reply from <net.> 192.35.51.30#53
--
1025674:Aug 09 14:43:09 unbound[644:0] info: resolving mail.secret-mailgui.de. A IN
1025675-Aug 09 14:43:15 unbound[644:0] info: resolving discourse-cdn.pi-hole.net. A IN
1025676-Aug 09 14:43:15 unbound[644:0] info: resolving discourse-cdn.pi-hole.net. A IN
1025677-Aug 09 14:43:15 unbound[644:0] info: response for discourse-cdn.pi-hole.net. A IN
--
1029103:Aug 09 14:44:49 unbound[644:0] info: resolving mail.secret-mailgui.de. A IN
1029104-Aug 09 14:44:51 unbound[644:0] info: resolving login.live.com. A IN
1029105-Aug 09 14:44:51 unbound[644:0] info: resolving ns3-34.azure-dns.org. A IN
1029106-Aug 09 14:44:51 unbound[644:0] info: resolving ns4-34.azure-dns.info. A IN
--
1034525:Aug 09 14:46:02 unbound[644:0] info: resolving mail.secret-mailgui.de. A IN
1034526-Aug 09 14:46:03 unbound[644:0] info: response for whatsapp.net. DS IN
1034527-Aug 09 14:46:03 unbound[644:0] info: reply from <net.> 192.35.51.30#53
1034528-Aug 09 14:46:03 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
--
1040248:Aug 09 14:48:00 unbound[644:0] info: resolving mail.secret-mailgui.de. A IN
1040249-Aug 09 14:48:00 unbound[644:0] info: response for edgekey.net. DS IN
1040250-Aug 09 14:48:00 unbound[644:0] info: reply from <net.> 192.12.94.30#53
1040251-Aug 09 14:48:00 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
--
1042785:Aug 09 14:48:59 unbound[644:0] info: resolving mail.secret-mailgui.de. A IN
1042786-Aug 09 14:48:59 unbound[644:0] info: response for mozaws.net. DS IN
1042787-Aug 09 14:48:59 unbound[644:0] info: reply from <net.> 192.41.162.30#53
1042788-Aug 09 14:48:59 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
--
1043689:Aug 09 14:49:21 unbound[644:0] info: resolving mail.secret-mailgui.de. A IN
1043690-Aug 09 14:49:21 unbound[644:0] info: response for pi-hole.net. DS IN
1043691-Aug 09 14:49:21 unbound[644:0] info: reply from <net.> 192.48.79.30#53
1043692-Aug 09 14:49:21 unbound[644:0] info: query response REC_LAME: recursive but not authoritative server
--
1044158:Aug 09 14:51:01 unbound[644:0] info: resolving mail.secret-mailgui.de. A IN
1044159-Aug 09 14:51:15 unbound[644:0] info: resolving autopush.prod.mozaws.net. A IN
1044160-Aug 09 14:51:15 unbound[644:0] info: response for autopush.prod.mozaws.net. A IN
1044161-Aug 09 14:51:15 unbound[644:0] info: reply from <prod.mozaws.net.> 205.251.194.102#53
--
1044961:Aug 09 14:59:09 unbound[644:0] info: resolving mail.secret-mailgui.de. A IN
1044962:Aug 09 14:59:09 unbound[644:0] info: response for mail.secret-mailgui.de. A IN
1044963:Aug 09 14:59:09 unbound[644:0] info: reply from <secret-mailgui.de.> 193.196.199.1#53
1044964-Aug 09 14:59:09 unbound[644:0] info: query response was LAME
1044965:Aug 09 14:59:09 unbound[644:0] info: response for mail.secret-mailgui.de. A IN
1044966:Aug 09 14:59:09 unbound[644:0] info: reply from <secret-mailgui.de.> 129.143.2.10#53
1044967-Aug 09 14:59:09 unbound[644:0] info: query response was LAME
1044968:Aug 09 14:59:09 unbound[644:0] info: response for mail.secret-mailgui.de. A IN
1044969:Aug 09 14:59:09 unbound[644:0] info: reply from <secret-mailgui.de.> 129.143.253.133#53
1044970-Aug 09 14:59:09 unbound[644:0] info: query response was LAME
1044971-Aug 09 14:59:25 unbound[644:0] info: resolving api.jdownloader.org. AAAA IN
1044972-Aug 09 14:59:25 unbound[644:0] info: response for api.jdownloader.org. AAAA IN
EDIT 2: Nach einem reboot des pi war das Problem wieder weg.
EDIT 3: Nach anderthalb Stunden besteht das Problem wieder, mit demselben Host.