Freifunk und DNS

Hallo, ich habe vor kurzem auf meinem Freifunk GW DNS eingerichtet - und habe das logging erst mal angelassen zur Fehlersuche - bekomme jetzt Fehlermeldungen wie:

2-Jun-2017 11:01:48.158 success resolving ‚vas.samsungapps.com/A‘ (in ‚samsungapps.com‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 14:34:04.325 success resolving ‚ns2.dns.com.cn/AAAA‘ (in ‚dns.com.cn‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 15:58:15.133 success resolving ‚ns2.dns.com.cn/AAAA‘ (in ‚dns.com.cn‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 16:20:37.518 success resolving ‚sdk.conf.igexin.com/A‘ (in ‚igexin.com‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 16:39:38.855 success resolving ‚ns1.dns.com.cn/A‘ (in ‚dns.com.cn‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 17:04:13.376 success resolving ‚fans.jstinno.com/A‘ (in ‚jstinno.com‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 22:20:38.417 success resolving ‚hmma.e.shifen.com/A‘ (in ‚e.shifen.com‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 22:57:16.074 success resolving ‚198.38.152.211.in-addr.arpa/PTR‘ (in ‚in-addr.arpa‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 23:09:49.178 success resolving ‚fans.jstinno.com/A‘ (in ‚jstinno.com‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 23:13:17.711 success resolving ‚dns3.ourdvs.org/AAAA‘ (in ‚ourdvs.org‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 23:13:17.712 success resolving ‚dns5.ourdvs.org/A‘ (in ‚ourdvs.org‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 23:13:17.712 success resolving ‚dns1.ourdvs.org/A‘ (in ‚ourdvs.org‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 23:13:17.712 success resolving ‚dns3.ourdvs.org/A‘ (in ‚ourdvs.org‘?) after reducing the advertised EDNS UDP packet size to 512 octets
12-Jun-2017 23:13:17.712 success resolving ‚dns1.ourdvs.org/AAAA‘ (in ‚ourdvs.org‘?) after reducing the advertised EDNS UDP packet size to 512 octets

09-Jun-2017 06:23:07.274 client 192.168.0.254#48106 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:09.179 client 192.168.0.254#48106 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:15.341 client 192.168.0.254#48221 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:17.360 client 192.168.0.254#48221 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:19.361 client 192.168.0.254#48221 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:25.421 client 192.168.0.254#57804 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:27.439 client 192.168.0.254#57804 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:29.443 client 192.168.0.254#57804 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:34.491 client 192.168.0.254#35129 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:36.501 client 192.168.0.254#35129 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:38.511 client 192.168.0.254#35129 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:44.584 client 192.168.0.254#41800 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:46.480 client 192.168.0.254#41800 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied
09-Jun-2017 06:23:48.494 client 192.168.0.254#41800 (a.root-servers.net): query (cache) ‚a.root-servers.net/A/IN‘ denied

Was mich wundert ist das ich nur 10.50.x.x IP’S vergebe und Ich Anfragen mit FremdIPS habe, kann ich da was gegen tun ( habe die Anfrage nur von 10.50.x.x erlaubt)

Du könntest jetzt den hier sonst üblichen Rant auf „dumme NutzerInnen, die Router falsch anschließen“ starten.
Oder eines der vielen EBTables-Pakete (viele Communities haben da was) in die Firmware einbauen, welche Alien/Rogue-Networks auf den Gluon-Knoten blockiert.

Wir nutzen kein Gluon, wobei es sicher mal ne Idee wäre solche IPS an unseren Routern zu blocken.