Intermitent failure to resolve local names

fellipec · November 16, 2020, 7:01pm

Expected Behaviour:

Resolve local hosts configured in pi-hole every single time when tested with nslookup.

Actual Behaviour:

Sometimes it reply with NXDOMAIN, sometimes no response, sometimes respond correctly:

pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

*** Can't find kos.lan: No answer

pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

*** Can't find kos.lan: No answer

pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

*** Can't find kos.lan: No answer

pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

Name:   kos.lan
Address: 192.168.100.38

pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

tail of the log with relevant part:

Nov 16 15:55:30 dnsmasq[5803]: query[AAAA] kos.lan from 192.168.100.3
Nov 16 15:55:30 dnsmasq[5803]: forwarded kos.lan to 1.0.0.1
Nov 16 15:55:30 dnsmasq[5803]: validation result is SECURE
Nov 16 15:55:30 dnsmasq[5803]: reply kos.lan is NODATA-IPv6

custom.list print

fellipec@aspireone:/etc/pihole$ cat custom.list
192.168.100.38 desktop-lfc.lan
192.168.100.2 aspireone.lan
192.168.100.1 router.lan
192.168.100.38 kos.lan

grep kos.lan pihole.log

Nov 16 14:38:26 dnsmasq[6256]: query[A] kos.lan.lan from 192.168.100.38
Nov 16 14:38:26 dnsmasq[6256]: forwarded kos.lan.lan to 1.1.1.1
Nov 16 14:38:26 dnsmasq[6256]: reply kos.lan.lan is NXDOMAIN
Nov 16 14:38:26 dnsmasq[6256]: query[AAAA] kos.lan.lan from 192.168.100.38
Nov 16 14:38:26 dnsmasq[6256]: forwarded kos.lan.lan to 1.1.1.1
Nov 16 14:38:26 dnsmasq[6256]: reply kos.lan.lan is NXDOMAIN
Nov 16 14:38:26 dnsmasq[6256]: query[A] kos.lan from 192.168.100.38
Nov 16 14:38:26 dnsmasq[6256]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 14:38:26 dnsmasq[6256]: query[AAAA] kos.lan from 192.168.100.38
Nov 16 14:38:26 dnsmasq[6256]: forwarded kos.lan to 1.1.1.1
Nov 16 14:38:26 dnsmasq[6256]: reply kos.lan is NODATA-IPv6
Nov 16 14:38:37 dnsmasq[6256]: query[A] kos.lan.lan from 192.168.100.38
Nov 16 14:38:37 dnsmasq[6256]: cached kos.lan.lan is NXDOMAIN
Nov 16 14:38:37 dnsmasq[6256]: query[AAAA] kos.lan.lan from 192.168.100.38
Nov 16 14:38:37 dnsmasq[6256]: cached kos.lan.lan is NXDOMAIN
Nov 16 14:38:37 dnsmasq[6256]: query[A] kos.lan from 192.168.100.38
Nov 16 14:38:37 dnsmasq[6256]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 14:38:37 dnsmasq[6256]: query[AAAA] kos.lan from 192.168.100.38
Nov 16 14:38:37 dnsmasq[6256]: cached kos.lan is NODATA-IPv6
Nov 16 14:39:01 dnsmasq[6256]: query[A] kos.lan.lan from 192.168.100.38
Nov 16 14:39:01 dnsmasq[6256]: cached kos.lan.lan is NXDOMAIN
Nov 16 14:39:01 dnsmasq[6256]: query[AAAA] kos.lan.lan from 192.168.100.38
Nov 16 14:39:01 dnsmasq[6256]: cached kos.lan.lan is NXDOMAIN
Nov 16 14:39:01 dnsmasq[6256]: query[A] kos.lan from 192.168.100.38
Nov 16 14:39:01 dnsmasq[6256]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 14:39:01 dnsmasq[6256]: query[AAAA] kos.lan from 192.168.100.38
Nov 16 14:39:01 dnsmasq[6256]: cached kos.lan is NODATA-IPv6
Nov 16 14:41:44 dnsmasq[6256]: query[A] kos.lan.lan from 192.168.100.38
Nov 16 14:41:44 dnsmasq[6256]: cached kos.lan.lan is NXDOMAIN
Nov 16 14:41:44 dnsmasq[6256]: query[AAAA] kos.lan.lan from 192.168.100.38
Nov 16 14:41:44 dnsmasq[6256]: cached kos.lan.lan is NXDOMAIN
Nov 16 14:41:44 dnsmasq[6256]: query[A] kos.lan from 192.168.100.38
Nov 16 14:41:44 dnsmasq[6256]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 14:41:44 dnsmasq[6256]: query[AAAA] kos.lan from 192.168.100.38
Nov 16 14:41:44 dnsmasq[6256]: cached kos.lan is NODATA-IPv6
Nov 16 14:42:25 dnsmasq[6256]: query[A] kos.lan from 192.168.100.2
Nov 16 14:42:25 dnsmasq[6256]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 14:42:25 dnsmasq[6256]: query[AAAA] kos.lan from 192.168.100.2
Nov 16 14:42:25 dnsmasq[6256]: cached kos.lan is NODATA-IPv6
Nov 16 14:45:12 dnsmasq[6256]: query[A] kos.lan from 192.168.100.3
Nov 16 14:45:12 dnsmasq[6256]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 14:45:12 dnsmasq[6256]: query[AAAA] kos.lan from 192.168.100.3
Nov 16 14:45:12 dnsmasq[6256]: cached kos.lan is NODATA-IPv6
Nov 16 14:45:33 dnsmasq[6256]: query[A] kos.lan from 192.168.100.3
Nov 16 14:45:33 dnsmasq[6256]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 14:45:33 dnsmasq[6256]: query[AAAA] kos.lan from 192.168.100.3
Nov 16 14:45:33 dnsmasq[6256]: cached kos.lan is NODATA-IPv6
Nov 16 14:45:43 dnsmasq[6256]: query[A] kos.lan from 192.168.100.3
Nov 16 14:45:43 dnsmasq[6256]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 14:45:43 dnsmasq[6256]: query[AAAA] kos.lan from 192.168.100.3
Nov 16 14:45:43 dnsmasq[6256]: cached kos.lan is NODATA-IPv6
Nov 16 15:10:35 dnsmasq[6256]: query[A] kos.lan from 192.168.100.3
Nov 16 15:10:35 dnsmasq[6256]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:10:35 dnsmasq[6256]: query[AAAA] kos.lan from 192.168.100.3
Nov 16 15:10:35 dnsmasq[6256]: cached kos.lan is NODATA-IPv6
Nov 16 15:28:54 dnsmasq[5803]: query[A] kos.lan from fdec:4d47:b3ab:b100::141
Nov 16 15:28:54 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:30:11 dnsmasq[5803]: query[A] kos.lan from fdec:4d47:b3ab:b100::141
Nov 16 15:30:11 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:30:19 dnsmasq[5803]: query[A] kos.lan from fdec:4d47:b3ab:b100::141
Nov 16 15:30:19 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:30:21 dnsmasq[5803]: query[A] kos.lan from 2001:1284:f013:5a7e:52a2:c544:6e0e:358d
Nov 16 15:30:21 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:30:22 dnsmasq[5803]: query[A] kos.lan from fdec:4d47:b3ab:b100::141
Nov 16 15:30:22 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:30:22 dnsmasq[5803]: query[A] kos.lan from 2001:1284:f013:5a7e:52a2:c544:6e0e:358d
Nov 16 15:30:22 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:35:36 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:35:36 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:36:11 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:36:11 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:36:28 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:36:28 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:36:33 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:36:33 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:36:35 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:36:35 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:36:37 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:36:37 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:36:42 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:36:42 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:37:15 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:37:15 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:37:36 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:37:36 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:38:01 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:38:01 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:38:04 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:38:04 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:38:13 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:38:13 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:38:15 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:38:15 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:38:16 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:38:16 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:38:18 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:38:18 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:38:21 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:38:21 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:44:52 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:44:52 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:44:55 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:44:55 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:44:57 dnsmasq[5803]: query[A] kos.lan from 192.168.100.3
Nov 16 15:44:57 dnsmasq[5803]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 15:55:30 dnsmasq[5803]: query[AAAA] kos.lan from 192.168.100.3
Nov 16 15:55:30 dnsmasq[5803]: forwarded kos.lan to 1.0.0.1
Nov 16 15:55:30 dnsmasq[5803]: reply kos.lan is NODATA-IPv6

Debug Token:

https://tricorder.pi-hole.net/sjiiwp2hkd

Edit: Added the grep part

DanSchaper · November 16, 2020, 7:22pm

fellipec:

Nov 16 15:55:30 dnsmasq[5803]: query[AAAA] kos.lan from 192.168.100.3
Nov 16 15:55:30 dnsmasq[5803]: forwarded kos.lan to 1.0.0.1
Nov 16 15:55:30 dnsmasq[5803]: validation result is SECURE
Nov 16 15:55:30 dnsmasq[5803]: reply kos.lan is NODATA-IPv6

That's just not possible. There is no way for a .lan domain to come back as SECURE from 1.0.0.1.

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=enp1s0
    IPV4_ADDRESS=192.168.100.2/24
    IPV6_ADDRESS=fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9
    QUERY_LOGGING=true
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=true
    BLOCKING_ENABLED=true
    DNSMASQ_LISTENING=single
    PIHOLE_DNS_1=208.67.222.222
    PIHOLE_DNS_2=208.67.220.220
    PIHOLE_DNS_3=2620:119:35::35
    PIHOLE_DNS_4=2620:119:53::53
    PIHOLE_DNS_5=4.2.2.1
    PIHOLE_DNS_6=4.2.2.2
    PIHOLE_DNS_7=84.200.69.80
    PIHOLE_DNS_8=84.200.70.40
    PIHOLE_DNS_9=2001:1608:10:25:0:0:1c04:b12f
    PIHOLE_DNS_10=2001:1608:10:25:0:0:9249:d69b
    PIHOLE_DNS_11=9.9.9.9
    PIHOLE_DNS_12=149.112.112.112
    PIHOLE_DNS_13=2620:fe::fe
    PIHOLE_DNS_14=2620:fe::9
    PIHOLE_DNS_15=1.1.1.1
    PIHOLE_DNS_16=1.0.0.1
    PIHOLE_DNS_17=2606:4700:4700::1111
    PIHOLE_DNS_18=2606:4700:4700::1001

There is no reason you should ever have 18 upstream servers. Ever.

Reset everything back to stock. Set Never forward non-FQDNs on the web interface.

fellipec · November 16, 2020, 7:27pm

Imagine my face when I read that. BTW never forward non-fqdn was checked.
Reduced the number of upstream servers to 4 (2 v4 and 2 v6)

DanSchaper · November 16, 2020, 7:30pm

dan@raspberrypi:~ $ dig +dnssec AAAA kos.lan @1.0.0.1

; <<>> DiG 9.11.5-P4-5.1+deb10u2-Raspbian <<>> +dnssec AAAA kos.lan @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 62525
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 6, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 1232
;; QUESTION SECTION:
;kos.lan.                       IN      AAAA

;; AUTHORITY SECTION:
.                       86400   IN      SOA     a.root-servers.net. nstld.verisign-grs.com. 2020111601 1800 900 604800 86400
.                       86400   IN      RRSIG   SOA 8 0 86400 20201129170000 20201116160000 26116 . IEkfBbIoZqOBvd6TNb0h7E7GruJW+owypC4eoA9XLsFScb+6k1tkIOkb VFFcJfxA/Lfy4PySWRFOO0xWzLQHBZwOu1zvQtj6pz5xDy61IOVR7V14 l7IYx6B1FwEuDaw8+ytQyXepVFee7V/1oua3O6Osg4KOechTTeiWnRxt cCTli10R3SZKt0LWeGBtd18nvIwIo1NoRy4nQ1DxyKN+e59kFeuTPyWY RDAFQ9o7/V18DqQ8xlqdeHBCU3ycQXdqAMn+C01VAf1OiwkEuECq+8+o 6L6K2ZNt2WuhfuTJ4w4BVezCUZDYWFgvfJthPGzdZ8KZn7KpD4tbDqrn AYIAPA==
lamer.                  86400   IN      NSEC    lancaster. NS DS RRSIG NSEC
lamer.                  86400   IN      RRSIG   NSEC 8 1 86400 20201129170000 20201116160000 26116 . t1FviLl2ljWba36VPOUbIDxO4WbNscqgLKYSXvTXCla+lWE9nFybbocw Hacc+QuOkFxV+Hc/x8U5a41R2ASY8W1IS+FLNhWGEa3Lbr7+ULnbdFwz kVHx4eGyg5zkTsL1SsBNAvBUQq9fB/udZUNswPEj5BGR9ZRCDYj42+YY 735pEfA75n4OwFRhSwYD8TtpYXa9gkP8b+HLvzW2+LmFlGthACvYECrg rZc1GGal6YHSKyvSrpeSSngisx9atrWdASUfDLlvyiOI6Nx63omkEgOV Qh0j59ZJWifK+fwuMVjsftfANcxA7hPfD1L8l7+a7PaOC6BefVANNgFh 8u2kGQ==
.                       86400   IN      NSEC    aaa. NS SOA RRSIG NSEC DNSKEY
.                       86400   IN      RRSIG   NSEC 8 0 86400 20201129170000 20201116160000 26116 . 0Ov508siKnm2DyyMeHL4E43s4NQUIUbbWxXVb69vNtepVjYwe5iqcQ/6 r/ODHTCpeneFo3FGERwxQEwqG9ajyxREfkm7S/BpfULgsZbJeA19LY8E ezG/uiQn/YXq5u/rGwDTwKjfQNgI/wCmrAgRPBw3dol2JseMIGHcc6XP 7+9vc3WMbpBw0HjSmbgvgtCULHyexXl50+MuNnjxAwcEVyIq1DFqKwUP HroItaH+yYNRrSbn1oCPtnVWohr4fov/j3CODRAGmVLkV9EXoQ69Cs03 CAeUpmeiioQAB7BuOM5kOj4hEl7G3LlwusrKdJwNR6oTUIP1S42dx07J dNvjXQ==

;; Query time: 14 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Mon Nov 16 11:29:34 PST 2020
;; MSG SIZE  rcvd: 1031

fellipec · November 16, 2020, 8:24pm

I just run pi-hole -r, let just Cloudflare DNS select, disable DNSSEC, checked that never forward FQDNs was enabled, restarted the machine and still get different results for the same query:

pi@netpink:~ $ dig @192.168.100.2 kos.lan

; <<>> DiG 9.11.5-P4-5.1+deb10u2-Debian <<>> @192.168.100.2 kos.lan
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 51612
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;kos.lan.                       IN      A

;; Query time: 3 msec
;; SERVER: 192.168.100.2#53(192.168.100.2)
;; WHEN: seg nov 16 16:59:10 -03 2020
;; MSG SIZE  rcvd: 36

pi@netpink:~ $ dig @192.168.100.2 kos.lan

; <<>> DiG 9.11.5-P4-5.1+deb10u2-Debian <<>> @192.168.100.2 kos.lan
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7770
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1280
;; QUESTION SECTION:
;kos.lan.                       IN      A

;; ANSWER SECTION:
kos.lan.                2       IN      A       192.168.100.38

;; Query time: 4 msec
;; SERVER: 192.168.100.2#53(192.168.100.2)
;; WHEN: seg nov 16 16:59:18 -03 2020
;; MSG SIZE  rcvd: 52

I generated another debug: https://tricorder.pi-hole.net/nq8posz7rw
And captured a print of the two terminals, one doing nslookups and the other with tail of pihole.log https://i.imgur.com/56GxqEM.png

PS: same happens if I use pi.hole, sometimes resolves, other return NXDOMAIN

fellipec · November 16, 2020, 8:31pm

Added timestamp to the linux prompt so can compare with the pihole.log

Nov 16 17:18:03 dnsmasq[29130]: forwarded www.googleapis.com to 1.1.1.1
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 172.217.29.10
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 172.217.28.234
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 172.217.162.106
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 172.217.30.74
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 172.217.172.202
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 172.217.30.170
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 172.217.162.138
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 172.217.28.138
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 172.217.29.138
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 172.217.29.234
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 216.58.202.138
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 172.217.162.202
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 216.58.202.202
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 216.58.202.10
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 172.217.172.138
Nov 16 17:18:03 dnsmasq[29130]: reply www.googleapis.com is 216.58.202.170
Nov 16 17:18:04 dnsmasq[29130]: query[AAAA] i.ytimg.com from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:18:04 dnsmasq[29130]: forwarded i.ytimg.com to 1.1.1.1
Nov 16 17:18:04 dnsmasq[29130]: reply i.ytimg.com is 2800:3f0:4001:806::2016
Nov 16 17:18:04 dnsmasq[29130]: query[A] i.ytimg.com from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:18:04 dnsmasq[29130]: forwarded i.ytimg.com to 1.1.1.1
Nov 16 17:18:04 dnsmasq[29130]: reply i.ytimg.com is 172.217.29.150
Nov 16 17:18:04 dnsmasq[29130]: query[AAAA] edge.microsoft.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:18:04 dnsmasq[29130]: cached edge.microsoft.com is <CNAME>
Nov 16 17:18:04 dnsmasq[29130]: cached edge-microsoft-com.a-0016.a-msedge.net is <CNAME>
Nov 16 17:18:04 dnsmasq[29130]: cached a-0016.a-msedge.net is NODATA-IPv6
Nov 16 17:18:05 dnsmasq[29130]: query[A] pi.hole from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:18:05 dnsmasq[29130]: /etc/pihole/local.list pi.hole is 192.168.100.2
Nov 16 17:18:05 dnsmasq[29130]: query[AAAA] pi.hole from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:18:05 dnsmasq[29130]: /etc/pihole/local.list pi.hole is fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9
Nov 16 17:18:05 dnsmasq[29130]: query[AAAA] googleads.g.doubleclick.net from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:18:05 dnsmasq[29130]: gravity blocked googleads.g.doubleclick.net is ::
Nov 16 17:18:05 dnsmasq[29130]: query[A] googleads.g.doubleclick.net from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:18:05 dnsmasq[29130]: gravity blocked googleads.g.doubleclick.net is 0.0.0.0
Nov 16 17:18:05 dnsmasq[29130]: query[AAAA] www.googleadservices.com from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:18:05 dnsmasq[29130]: gravity blocked www.googleadservices.com is ::
Nov 16 17:18:05 dnsmasq[29130]: query[A] www.googleadservices.com from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:18:05 dnsmasq[29130]: gravity blocked www.googleadservices.com is 0.0.0.0
Nov 16 17:18:18 dnsmasq[29130]: query[AAAA] discourse.pi-hole.net from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:18:18 dnsmasq[29130]: cached discourse.pi-hole.net is NODATA-IPv6
Nov 16 17:18:24 dnsmasq[29130]: query[AAAA] web.whatsapp.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:18:24 dnsmasq[29130]: cached web.whatsapp.com is <CNAME>
Nov 16 17:18:24 dnsmasq[29130]: forwarded web.whatsapp.com to 1.1.1.1
Nov 16 17:18:24 dnsmasq[29130]: query[A] web.whatsapp.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:18:24 dnsmasq[29130]: forwarded web.whatsapp.com to 1.1.1.1
Nov 16 17:18:24 dnsmasq[29130]: reply web.whatsapp.com is <CNAME>
Nov 16 17:18:24 dnsmasq[29130]: reply mmx-ds.cdn.whatsapp.net is 2a03:2880:f248:c7:face:b00c:0:167
Nov 16 17:18:24 dnsmasq[29130]: reply web.whatsapp.com is <CNAME>
Nov 16 17:18:24 dnsmasq[29130]: reply mmx-ds.cdn.whatsapp.net is 31.13.85.51
Nov 16 17:18:24 dnsmasq[29130]: query[A] client.dropbox.com from 192.168.100.3
Nov 16 17:18:24 dnsmasq[29130]: forwarded client.dropbox.com to 1.1.1.1
Nov 16 17:18:24 dnsmasq[29130]: query[AAAA] client.dropbox.com from 192.168.100.3
Nov 16 17:18:24 dnsmasq[29130]: forwarded client.dropbox.com to 1.1.1.1
Nov 16 17:18:24 dnsmasq[29130]: reply client.dropbox.com is <CNAME>
Nov 16 17:18:24 dnsmasq[29130]: reply client-env.dropbox-dns.com is 162.125.5.13
Nov 16 17:18:24 dnsmasq[29130]: reply client.dropbox.com is <CNAME>
Nov 16 17:18:24 dnsmasq[29130]: reply client-env.dropbox-dns.com is 2620:100:601d:13::a27d:50d
Nov 16 17:18:24 dnsmasq[29130]: query[AAAA] www.bing.com from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:18:24 dnsmasq[29130]: forwarded www.bing.com to 1.1.1.1
Nov 16 17:18:24 dnsmasq[29130]: reply www.bing.com is <CNAME>
Nov 16 17:18:24 dnsmasq[29130]: reply a-0001.a-afdentry.net.trafficmanager.net is <CNAME>
Nov 16 17:18:24 dnsmasq[29130]: reply dual-a-0001.a-msedge.net is 2620:1ec:c11::200
Nov 16 17:18:24 dnsmasq[29130]: query[A] www.bing.com from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:18:24 dnsmasq[29130]: cached www.bing.com is <CNAME>
Nov 16 17:18:24 dnsmasq[29130]: cached a-0001.a-afdentry.net.trafficmanager.net is <CNAME>
Nov 16 17:18:24 dnsmasq[29130]: forwarded www.bing.com to 1.1.1.1
Nov 16 17:18:24 dnsmasq[29130]: reply www.bing.com is <CNAME>
Nov 16 17:18:24 dnsmasq[29130]: reply a-0001.a-afdentry.net.trafficmanager.net is <CNAME>
Nov 16 17:18:24 dnsmasq[29130]: reply dual-a-0001.a-msedge.net is 13.107.21.200
Nov 16 17:18:24 dnsmasq[29130]: reply dual-a-0001.a-msedge.net is 204.79.197.200
Nov 16 17:18:25 dnsmasq[29130]: query[AAAA] in.appcenter.ms from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:18:25 dnsmasq[29130]: forwarded in.appcenter.ms to 1.1.1.1
Nov 16 17:18:25 dnsmasq[29130]: reply in.appcenter.ms is <CNAME>
Nov 16 17:18:25 dnsmasq[29130]: reply in2-prod-east-us2-23fa330.trafficmanager.net is <CNAME>
Nov 16 17:18:25 dnsmasq[29130]: reply in2-gw2-01-51193e94.eastus.cloudapp.azure.com is NODATA-IPv6
Nov 16 17:18:25 dnsmasq[29130]: query[A] in.appcenter.ms from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:18:25 dnsmasq[29130]: cached in.appcenter.ms is <CNAME>
Nov 16 17:18:25 dnsmasq[29130]: cached in2-prod-east-us2-23fa330.trafficmanager.net is <CNAME>
Nov 16 17:18:25 dnsmasq[29130]: forwarded in.appcenter.ms to 1.1.1.1
Nov 16 17:18:25 dnsmasq[29130]: reply in.appcenter.ms is <CNAME>
Nov 16 17:18:25 dnsmasq[29130]: reply in2-prod-east-us2-23fa330.trafficmanager.net is <CNAME>
Nov 16 17:18:25 dnsmasq[29130]: reply in2-gw2-01-51193e94.eastus.cloudapp.azure.com is 20.185.73.23
Nov 16 17:18:31 dnsmasq[29130]: query[A] pi.hole from 192.168.100.3
Nov 16 17:18:31 dnsmasq[29130]: /etc/pihole/local.list pi.hole is 192.168.100.2
Nov 16 17:18:31 dnsmasq[29130]: query[AAAA] pi.hole from 192.168.100.3
Nov 16 17:18:31 dnsmasq[29130]: /etc/pihole/local.list pi.hole is fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9
Nov 16 17:18:34 dnsmasq[29130]: query[A] graph.microsoft.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:18:34 dnsmasq[29130]: forwarded graph.microsoft.com to 1.1.1.1
Nov 16 17:18:34 dnsmasq[29130]: query[AAAA] graph.microsoft.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:18:34 dnsmasq[29130]: forwarded graph.microsoft.com to 1.1.1.1
Nov 16 17:18:34 dnsmasq[29130]: reply graph.microsoft.com is <CNAME>
Nov 16 17:18:34 dnsmasq[29130]: reply ags.privatelink.msidentity.com is <CNAME>
Nov 16 17:18:34 dnsmasq[29130]: reply prd.ags.msidentity.com is 20.190.145.49
Nov 16 17:18:34 dnsmasq[29130]: reply prd.ags.msidentity.com is 20.190.145.50
Nov 16 17:18:34 dnsmasq[29130]: reply prd.ags.msidentity.com is 20.190.145.51
Nov 16 17:18:34 dnsmasq[29130]: reply graph.microsoft.com is <CNAME>
Nov 16 17:18:34 dnsmasq[29130]: reply ags.privatelink.msidentity.com is <CNAME>
Nov 16 17:18:34 dnsmasq[29130]: reply prd.ags.msidentity.com is <CNAME>
Nov 16 17:18:34 dnsmasq[29130]: reply www.tm.prd.ags.akadns.net is NODATA-IPv6
Nov 16 17:18:34 dnsmasq[29130]: query[AAAA] aka.ms from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:18:34 dnsmasq[29130]: cached aka.ms is NODATA-IPv6
Nov 16 17:18:34 dnsmasq[29130]: query[A] aka.ms from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:18:34 dnsmasq[29130]: forwarded aka.ms to 1.1.1.1
Nov 16 17:18:34 dnsmasq[29130]: reply aka.ms is 173.222.158.207
Nov 16 17:18:34 dnsmasq[29130]: query[A] catalog.gamepass.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:18:34 dnsmasq[29130]: cached catalog.gamepass.com is <CNAME>
Nov 16 17:18:34 dnsmasq[29130]: cached catalog.gamepass.com.edgesuite.net is <CNAME>
Nov 16 17:18:34 dnsmasq[29130]: forwarded catalog.gamepass.com to 1.1.1.1
Nov 16 17:18:34 dnsmasq[29130]: query[AAAA] catalog.gamepass.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:18:34 dnsmasq[29130]: cached catalog.gamepass.com is <CNAME>
Nov 16 17:18:34 dnsmasq[29130]: forwarded catalog.gamepass.com to 1.1.1.1
Nov 16 17:18:34 dnsmasq[29130]: reply catalog.gamepass.com is <CNAME>
Nov 16 17:18:34 dnsmasq[29130]: reply catalog.gamepass.com.edgesuite.net is <CNAME>
Nov 16 17:18:34 dnsmasq[29130]: reply a1992.dscd.akamai.net is 23.63.28.219
Nov 16 17:18:34 dnsmasq[29130]: reply a1992.dscd.akamai.net is 23.63.28.211
Nov 16 17:18:34 dnsmasq[29130]: reply catalog.gamepass.com is <CNAME>
Nov 16 17:18:34 dnsmasq[29130]: reply catalog.gamepass.com.edgesuite.net is <CNAME>
Nov 16 17:18:34 dnsmasq[29130]: reply a1992.dscd.akamai.net is 2600:1419:ac00::172d:e18
Nov 16 17:18:34 dnsmasq[29130]: reply a1992.dscd.akamai.net is 2600:1419:ac00::172d:e09
Nov 16 17:18:38 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:18:38 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:18:39 dnsmasq[29130]: query[AAAA] substrate.office.com from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:18:39 dnsmasq[29130]: forwarded substrate.office.com to 1.1.1.1
Nov 16 17:18:39 dnsmasq[29130]: reply substrate.office.com is <CNAME>
Nov 16 17:18:39 dnsmasq[29130]: reply substrate.ms-acdc.office.com is <CNAME>
Nov 16 17:18:39 dnsmasq[29130]: reply outlook.ha.office365.com is <CNAME>
Nov 16 17:18:39 dnsmasq[29130]: reply outlook.ms-acdc.office.com is <CNAME>
Nov 16 17:18:39 dnsmasq[29130]: reply CPQ-efz.ms-acdc.office.com is 2603:1056:400:1::2
Nov 16 17:18:39 dnsmasq[29130]: reply CPQ-efz.ms-acdc.office.com is 2603:1056:c03:1000::2
Nov 16 17:18:39 dnsmasq[29130]: reply CPQ-efz.ms-acdc.office.com is 2603:1056:402:1c::2
Nov 16 17:18:39 dnsmasq[29130]: reply CPQ-efz.ms-acdc.office.com is 2603:1056:402::2
Nov 16 17:18:39 dnsmasq[29130]: query[A] substrate.office.com from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:18:39 dnsmasq[29130]: cached substrate.office.com is <CNAME>
Nov 16 17:18:39 dnsmasq[29130]: cached substrate.ms-acdc.office.com is <CNAME>
Nov 16 17:18:39 dnsmasq[29130]: cached outlook.ha.office365.com is <CNAME>
Nov 16 17:18:39 dnsmasq[29130]: cached outlook.ms-acdc.office.com is <CNAME>
Nov 16 17:18:39 dnsmasq[29130]: forwarded substrate.office.com to 1.1.1.1
Nov 16 17:18:39 dnsmasq[29130]: reply substrate.office.com is <CNAME>
Nov 16 17:18:39 dnsmasq[29130]: reply substrate.ms-acdc.office.com is <CNAME>
Nov 16 17:18:39 dnsmasq[29130]: reply outlook.ha.office365.com is <CNAME>
Nov 16 17:18:39 dnsmasq[29130]: reply outlook.ms-acdc.office.com is <CNAME>
Nov 16 17:18:39 dnsmasq[29130]: reply CPQ-efz.ms-acdc.office.com is 52.97.11.82
Nov 16 17:18:39 dnsmasq[29130]: reply CPQ-efz.ms-acdc.office.com is 52.97.67.98
Nov 16 17:18:39 dnsmasq[29130]: reply CPQ-efz.ms-acdc.office.com is 52.97.67.130
Nov 16 17:18:39 dnsmasq[29130]: reply CPQ-efz.ms-acdc.office.com is 52.97.67.210
Nov 16 17:18:40 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:18:40 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:18:42 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:18:42 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:18:44 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:18:44 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:18:46 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:18:46 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:19:06 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:19:06 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:19:13 dnsmasq[29130]: query[A] ctldl.windowsupdate.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:13 dnsmasq[29130]: forwarded ctldl.windowsupdate.com to 1.1.1.1
Nov 16 17:19:13 dnsmasq[29130]: query[AAAA] ctldl.windowsupdate.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:13 dnsmasq[29130]: forwarded ctldl.windowsupdate.com to 1.1.1.1
Nov 16 17:19:13 dnsmasq[29130]: reply ctldl.windowsupdate.com is <CNAME>
Nov 16 17:19:13 dnsmasq[29130]: reply au-bg-shim.trafficmanager.net is <CNAME>
Nov 16 17:19:13 dnsmasq[29130]: reply audownload.windowsupdate.nsatc.net is <CNAME>
Nov 16 17:19:13 dnsmasq[29130]: reply auto.au.download.windowsupdate.com.c.footprint.net is 8.241.216.126
Nov 16 17:19:13 dnsmasq[29130]: reply auto.au.download.windowsupdate.com.c.footprint.net is 8.241.211.126
Nov 16 17:19:13 dnsmasq[29130]: reply auto.au.download.windowsupdate.com.c.footprint.net is 8.241.215.254
Nov 16 17:19:13 dnsmasq[29130]: reply auto.au.download.windowsupdate.com.c.footprint.net is 8.241.198.254
Nov 16 17:19:13 dnsmasq[29130]: reply auto.au.download.windowsupdate.com.c.footprint.net is 8.241.212.254
Nov 16 17:19:13 dnsmasq[29130]: reply ctldl.windowsupdate.com is <CNAME>
Nov 16 17:19:13 dnsmasq[29130]: reply au-bg-shim.trafficmanager.net is <CNAME>
Nov 16 17:19:13 dnsmasq[29130]: reply audownload.windowsupdate.nsatc.net is <CNAME>
Nov 16 17:19:13 dnsmasq[29130]: reply auto.au.download.windowsupdate.com.c.footprint.net is 2620:11b:e029:3::1fe
Nov 16 17:19:13 dnsmasq[29130]: reply auto.au.download.windowsupdate.com.c.footprint.net is 2620:11b:e029:4::1fe
Nov 16 17:19:13 dnsmasq[29130]: reply auto.au.download.windowsupdate.com.c.footprint.net is 2001:1900:2341:27::1fe
Nov 16 17:19:13 dnsmasq[29130]: reply auto.au.download.windowsupdate.com.c.footprint.net is 2001:1900:2341:1b::1fe
Nov 16 17:19:13 dnsmasq[29130]: reply auto.au.download.windowsupdate.com.c.footprint.net is 2001:1900:2341:23::1fe
Nov 16 17:19:13 dnsmasq[29130]: query[A] ocsp05.actalis.it from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:13 dnsmasq[29130]: forwarded ocsp05.actalis.it to 1.1.1.1
Nov 16 17:19:13 dnsmasq[29130]: query[AAAA] ocsp05.actalis.it from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:13 dnsmasq[29130]: forwarded ocsp05.actalis.it to 1.1.1.1
Nov 16 17:19:13 dnsmasq[29130]: reply ocsp05.actalis.it is <CNAME>
Nov 16 17:19:13 dnsmasq[29130]: reply ocsp.actalis.it is NODATA-IPv6
Nov 16 17:19:13 dnsmasq[29130]: reply ocsp05.actalis.it is <CNAME>
Nov 16 17:19:13 dnsmasq[29130]: reply ocsp.actalis.it is 109.70.240.130
Nov 16 17:19:14 dnsmasq[29130]: query[A] presence.gog.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:14 dnsmasq[29130]: cached presence.gog.com is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: cached gog.com.edgekey.net is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: forwarded presence.gog.com to 1.1.1.1
Nov 16 17:19:14 dnsmasq[29130]: query[AAAA] presence.gog.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:14 dnsmasq[29130]: cached presence.gog.com is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: cached gog.com.edgekey.net is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: cached e11072.b.akamaiedge.net is NODATA-IPv6
Nov 16 17:19:14 dnsmasq[29130]: query[A] presence.gog.com from 192.168.100.38
Nov 16 17:19:14 dnsmasq[29130]: cached presence.gog.com is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: cached gog.com.edgekey.net is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: forwarded presence.gog.com to 1.1.1.1
Nov 16 17:19:14 dnsmasq[29130]: query[A] crl.pki.goog from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:14 dnsmasq[29130]: forwarded crl.pki.goog to 1.1.1.1
Nov 16 17:19:14 dnsmasq[29130]: query[AAAA] crl.pki.goog from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:14 dnsmasq[29130]: forwarded crl.pki.goog to 1.1.1.1
Nov 16 17:19:14 dnsmasq[29130]: reply crl.pki.goog is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: reply pki-goog.l.google.com is 216.58.202.131
Nov 16 17:19:14 dnsmasq[29130]: reply crl.pki.goog is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: reply pki-goog.l.google.com is 2800:3f0:4001:813::2003
Nov 16 17:19:14 dnsmasq[29130]: query[A] crl.globalsign.net from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:14 dnsmasq[29130]: forwarded crl.globalsign.net to 1.1.1.1
Nov 16 17:19:14 dnsmasq[29130]: query[AAAA] crl.globalsign.net from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:14 dnsmasq[29130]: forwarded crl.globalsign.net to 1.1.1.1
Nov 16 17:19:14 dnsmasq[29130]: reply crl.globalsign.net is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: reply global.prd.cdn.globalsign.com is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: reply cdn.globalsigncdn.com.cdn.cloudflare.net is 104.18.20.226
Nov 16 17:19:14 dnsmasq[29130]: reply cdn.globalsigncdn.com.cdn.cloudflare.net is 104.18.21.226
Nov 16 17:19:14 dnsmasq[29130]: reply crl.globalsign.net is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: reply global.prd.cdn.globalsign.com is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: reply cdn.globalsigncdn.com.cdn.cloudflare.net is 2606:4700::6812:14e2
Nov 16 17:19:14 dnsmasq[29130]: reply cdn.globalsigncdn.com.cdn.cloudflare.net is 2606:4700::6812:15e2
Nov 16 17:19:14 dnsmasq[29130]: reply presence.gog.com is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: reply gog.com.edgekey.net is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: reply e11072.b.akamaiedge.net is 173.222.158.50
Nov 16 17:19:14 dnsmasq[29130]: reply presence.gog.com is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: reply gog.com.edgekey.net is <CNAME>
Nov 16 17:19:14 dnsmasq[29130]: reply e11072.b.akamaiedge.net is 173.222.158.50
Nov 16 17:19:21 dnsmasq[29130]: query[A] account-public-service-prod03.ol.epicgames.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:21 dnsmasq[29130]: forwarded account-public-service-prod03.ol.epicgames.com to 1.1.1.1
Nov 16 17:19:21 dnsmasq[29130]: reply account-public-service-prod03.ol.epicgames.com is 3.87.233.152
Nov 16 17:19:21 dnsmasq[29130]: reply account-public-service-prod03.ol.epicgames.com is 23.21.108.40
Nov 16 17:19:21 dnsmasq[29130]: reply account-public-service-prod03.ol.epicgames.com is 54.162.122.85
Nov 16 17:19:21 dnsmasq[29130]: reply account-public-service-prod03.ol.epicgames.com is 54.174.31.52
Nov 16 17:19:21 dnsmasq[29130]: reply account-public-service-prod03.ol.epicgames.com is 18.210.194.48
Nov 16 17:19:21 dnsmasq[29130]: reply account-public-service-prod03.ol.epicgames.com is 52.1.97.140
Nov 16 17:19:21 dnsmasq[29130]: reply account-public-service-prod03.ol.epicgames.com is 35.168.168.42
Nov 16 17:19:21 dnsmasq[29130]: reply account-public-service-prod03.ol.epicgames.com is 18.214.225.62
Nov 16 17:19:28 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:19:28 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:19:38 dnsmasq[29130]: query[AAAA] az764295.vo.msecnd.net from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:38 dnsmasq[29130]: cached az764295.vo.msecnd.net is <CNAME>
Nov 16 17:19:38 dnsmasq[29130]: forwarded az764295.vo.msecnd.net to 1.1.1.1
Nov 16 17:19:38 dnsmasq[29130]: reply az764295.vo.msecnd.net is <CNAME>
Nov 16 17:19:38 dnsmasq[29130]: reply cs22.wpc.v0cdn.net is NODATA-IPv6
Nov 16 17:19:46 dnsmasq[29130]: query[A] pi.hole from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:46 dnsmasq[29130]: /etc/pihole/local.list pi.hole is 192.168.100.2
Nov 16 17:19:46 dnsmasq[29130]: query[AAAA] pi.hole from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:46 dnsmasq[29130]: /etc/pihole/local.list pi.hole is fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9
Nov 16 17:19:47 dnsmasq[29130]: query[A] vortex.data.microsoft.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:47 dnsmasq[29130]: cached vortex.data.microsoft.com is <CNAME>
Nov 16 17:19:47 dnsmasq[29130]: forwarded vortex.data.microsoft.com to 1.1.1.1
Nov 16 17:19:47 dnsmasq[29130]: query[AAAA] vortex.data.microsoft.com from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:47 dnsmasq[29130]: forwarded vortex.data.microsoft.com to 1.1.1.1
Nov 16 17:19:47 dnsmasq[29130]: reply vortex.data.microsoft.com is <CNAME>
Nov 16 17:19:47 dnsmasq[29130]: reply asimov.vortex.data.trafficmanager.net is 64.4.54.254
Nov 16 17:19:47 dnsmasq[29130]: reply vortex.data.microsoft.com is <CNAME>
Nov 16 17:19:47 dnsmasq[29130]: reply asimov.vortex.data.trafficmanager.net is <CNAME>
Nov 16 17:19:47 dnsmasq[29130]: reply global.vortex.data.trafficmanager.net is NODATA-IPv6
Nov 16 17:19:48 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:19:48 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:19:51 dnsmasq[29130]: query[AAAA] gateway.discord.gg from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:51 dnsmasq[29130]: forwarded gateway.discord.gg to 1.1.1.1
Nov 16 17:19:51 dnsmasq[29130]: query[A] gateway.discord.gg from fdec:4d47:b3ab:b100:d0a1:152:8273:5aeb
Nov 16 17:19:51 dnsmasq[29130]: forwarded gateway.discord.gg to 1.1.1.1
Nov 16 17:19:51 dnsmasq[29130]: reply gateway.discord.gg is NODATA-IPv6
Nov 16 17:19:51 dnsmasq[29130]: reply gateway.discord.gg is 162.159.133.234
Nov 16 17:19:51 dnsmasq[29130]: reply gateway.discord.gg is 162.159.135.234
Nov 16 17:19:51 dnsmasq[29130]: reply gateway.discord.gg is 162.159.134.234
Nov 16 17:19:51 dnsmasq[29130]: reply gateway.discord.gg is 162.159.136.234
Nov 16 17:19:51 dnsmasq[29130]: reply gateway.discord.gg is 162.159.130.234
Nov 16 17:19:56 dnsmasq[29130]: query[AAAA] graph.instagram.com from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:19:56 dnsmasq[29130]: cached graph.instagram.com is <CNAME>
Nov 16 17:19:56 dnsmasq[29130]: forwarded graph.instagram.com to 1.1.1.1
Nov 16 17:19:56 dnsmasq[29130]: reply graph.instagram.com is <CNAME>
Nov 16 17:19:56 dnsmasq[29130]: reply instagram.c10r.facebook.com is 2a03:2880:f205:c4:face:b00c:0:43fe
Nov 16 17:19:56 dnsmasq[29130]: query[A] graph.instagram.com from 2001:1284:f013:5a7e:60b3:7bc:7b7c:e2ad
Nov 16 17:19:56 dnsmasq[29130]: cached graph.instagram.com is <CNAME>
Nov 16 17:19:56 dnsmasq[29130]: forwarded graph.instagram.com to 1.1.1.1
Nov 16 17:19:56 dnsmasq[29130]: reply graph.instagram.com is <CNAME>
Nov 16 17:19:56 dnsmasq[29130]: reply instagram.c10r.facebook.com is 157.240.222.63


[2020-11-16-17:18:42] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   kos.lan
Address: 192.168.100.38
** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:43] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

Name:   kos.lan
Address: 192.168.100.38
** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:44] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   kos.lan
Address: 192.168.100.38
** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:44] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   kos.lan
Address: 192.168.100.38
** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:45] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:46] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:46] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:47] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:48] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:48] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:49] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:49] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:50] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:51] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:51] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:52] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:52] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:53] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:53] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:54] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:54] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:55] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:55] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:56] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:56] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:57] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:57] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:58] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:59] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:18:59] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:01] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:02] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:02] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:03] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:03] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:04] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:04] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:04] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:05] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:05] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:06] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:06] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:07] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:07] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:08] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:08] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:09] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:09] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:10] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:10] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:11] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:14] pi@netpink:~ $
[2020-11-16-17:19:16] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:19] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:21] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:23] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:24] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:25] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:26] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:28] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:29] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:30] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:31] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:36] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:37] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:37] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:39] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:40] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:41] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:41] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:42] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:42] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:43] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:44] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:45] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:46] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:46] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:47] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:48] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:51] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:52] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:53] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:53] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:54] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:54] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:55] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

[2020-11-16-17:19:56] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:57] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:57] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:58] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:59] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
^[[AServer:             192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:59] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

[2020-11-16-17:19:59] pi@netpink:~ $ nslookup pi.hole 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find pi.hole: NXDOMAIN

DanSchaper · November 16, 2020, 8:35pm

I don't know what I'm supposed to be looking at.

I'll let someone that has some spare time step in and see if they can unwind everything.

DanSchaper · November 16, 2020, 8:37pm

All I see is:

Nov 16 17:18:38 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:18:38 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:18:40 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:18:40 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:18:42 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:18:42 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:18:44 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:18:44 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:18:46 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:18:46 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:19:06 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:19:06 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:19:28 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:19:28 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38
Nov 16 17:19:48 dnsmasq[29130]: query[A] kos.lan from 192.168.100.3
Nov 16 17:19:48 dnsmasq[29130]: /etc/pihole/custom.list kos.lan is 192.168.100.38

fellipec · November 16, 2020, 8:38pm

Neither me, never seen something like that before. Anyway appreciate your time Dan, thank you.

DanSchaper · November 16, 2020, 8:39pm

fellipec:

[2020-11-16-17:18:44] pi@netpink:~ $ nslookup kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   kos.lan
Address: 192.168.100.38
** server can't find kos.lan: NXDOMAIN

That's a valid answer, it's telling you the IP address.

DanSchaper · November 16, 2020, 8:42pm

Give this a try:

nslookup -type=a kos.lan 192.168.100.2
nslookup -type=aaaa kos.lan 192.168.100.2

I think your response is showing that there is an A record but there is no AAAA.

DanSchaper · November 16, 2020, 8:49pm

Lastly, try disabling DHCPv6, I don't think you have it set up correctly:

   dhcp-option=option6:dns-server,[::]
   dhcp-range=::100,::1ff,constructor:enp1s0,ra-names,slaac,1h
   ra-param=*,0,0

You're advertising localhost as the dns-server, which won't work on clients.

Check a client and see what DNS servers they are configured to use.

fellipec · November 16, 2020, 8:57pm

Exactly, sometimes it answers, sometimes not. I can't even tell when this started, noticed today when ssh'd that kos.lan host, and said couldn't resolve the name. tried again a couple of times and it connected. After doing what I had to do, I decided to check why it failed and found this weird behavior.

Now I fired wireshark to try to find an answer. For a few dozen times it replied correctly, I even thought the problem fixed itself. But then started to return NXDOMAIN again, in wireshark I saw "Standard query response 0x560F No such name A kos.lan"

I did the tests you asked me:

[2020-11-16-17:45:59] pi@netpink:~ $ nslookup -type=aaaa kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
*** Can't find kos.lan: No answer

[2020-11-16-17:46:04] pi@netpink:~ $ nslookup -type=a kos.lan 192.168.100.2
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

Also here the IP address of the pi-hole server:

fellipec@aspireone:/var/log$ ip addr
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 88:ae:1d:a4:cd:b5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.2/24 brd 192.168.100.255 scope global noprefixroute enp1s0
       valid_lft forever preferred_lft forever
    inet6 fdec:4d47:b3ab:b100::1c7/128 scope global dynamic noprefixroute
       valid_lft 2387sec preferred_lft 2387sec
    inet6 2001:1284:f013:5a7e::1c7/128 scope global dynamic noprefixroute
       valid_lft 2387sec preferred_lft 2387sec
    inet6 2001:1284:f013:5a7e:940a:8180:e3e7:997e/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 86191sec preferred_lft 86191sec
    inet6 fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 6991sec preferred_lft 3391sec
    inet6 fe80::dbc4:eb5e:e594:7e46/64 scope link
       valid_lft forever preferred_lft forever
fellipec@aspireone:/var/log$

And here the ip configuration of the client computer

[2020-11-16-17:55:00] pi@netpink:~ $ ip addr
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:26:5e:49:53:43 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.39/24 brd 192.168.100.255 scope global dynamic noprefixroute wlan0
       valid_lft 2902sec preferred_lft 2304sec
    inet6 fdec:4d47:b3ab:b100::141/128 scope global dynamic noprefixroute
       valid_lft 2865sec preferred_lft 2865sec
    inet6 fdec:4d47:b3ab:b100:8065:e513:d0e8:fcd9/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 3370sec preferred_lft 3310sec
    inet6 2001:1284:f013:5a7e:52a2:c544:6e0e:358d/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 3370sec preferred_lft 3370sec
    inet6 fe80::fcc4:8a0c:c210:e5c3/64 scope link
       valid_lft forever preferred_lft forever
[2020-11-16-17:55:03] pi@netpink:~ $ cat /etc/resolv.conf
# Generated by resolvconf
domain lan
nameserver 192.168.100.2
nameserver fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9
nameserver 2001:1284:f013:5a7e::1c7

This part looks correct to me. I also don't know how can configure (wrong or right) IPv6 in pi-hole because is just enable or disable checkbox.

DanSchaper · November 16, 2020, 9:02pm

Who is that? Doesn't look to be an IP on Pi-hole. If it's the router or the ISP then you will get NXDOMAIN responses when that client asks for kos.lan. There are no primary/secondary DNS addresses, any namesever listed in resolv.conf will be used. That would explain the random NXDOMAIN responses, those are the times the cleint is asking 2001:1284:f013:5a7e::1c7 for the query.

DanSchaper · November 16, 2020, 9:04pm

What will make it all a ton easier would be to completely remove IPv6 from your LAN. If Pi-hole works fine on pure IPv4 then we're halfway to knowing where the issue is.

fellipec · November 16, 2020, 9:10pm

It's the pi-hole server, the second ipnet6 address listed

inet6 2001:1284:f013:5a7e::1c7/128 scope global dynamic noprefixroute
       valid_lft 2387sec preferred_lft 2387sec

fellipec · November 16, 2020, 9:21pm

I can't remove ipv6 from entire network but I can disable from just a machine. Anyways I started testing with nslookup expliciting asking for the ipv4 address of the pi-hole to avoid such rabbit holes.

Anyway, disabled the ipv6 on the client machine, and made a bash script to query kos.lan, pi.hole and google.com in a loop.

At first it didn't resolve kos.lan, but the other two domains worked. After a some queries it started to work:

[2020-11-16-18:15:03] pi@netpink:~ $ bash test.sh
Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

Server:         192.168.100.2
Address:        192.168.100.2#53

Name:   pi.hole
Address: 192.168.100.2
Name:   pi.hole
Address: fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   google.com
Address: 172.217.28.14
Name:   google.com
Address: 2800:3f0:4001:810::200e

Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   pi.hole
Address: 192.168.100.2
Name:   pi.hole
Address: fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   google.com
Address: 172.217.28.14
Name:   google.com
Address: 2800:3f0:4001:810::200e

Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   pi.hole
Address: 192.168.100.2
Name:   pi.hole
Address: fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   google.com
Address: 172.217.28.14
Name:   google.com
Address: 2800:3f0:4001:810::200e

Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   pi.hole
Address: 192.168.100.2
Name:   pi.hole
Address: fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   google.com
Address: 172.217.28.14
Name:   google.com
Address: 2800:3f0:4001:810::200e

Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   pi.hole
Address: 192.168.100.2
Name:   pi.hole
Address: fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   google.com
Address: 172.217.28.14
Name:   google.com
Address: 2800:3f0:4001:810::200e

Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   pi.hole
Address: 192.168.100.2
Name:   pi.hole
Address: fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   google.com
Address: 172.217.28.14
Name:   google.com
Address: 2800:3f0:4001:810::200e

Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   pi.hole
Address: 192.168.100.2
Name:   pi.hole
Address: fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   google.com
Address: 172.217.28.14
Name:   google.com
Address: 2800:3f0:4001:810::200e

Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   pi.hole
Address: 192.168.100.2
Name:   pi.hole
Address: fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   google.com
Address: 172.217.28.14
Name:   google.com
Address: 2800:3f0:4001:810::200e

Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   pi.hole
Address: 192.168.100.2
Name:   pi.hole
Address: fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   google.com
Address: 172.217.28.14
Name:   google.com
Address: 2800:3f0:4001:810::200e

Server:         192.168.100.2
Address:        192.168.100.2#53

** server can't find kos.lan: NXDOMAIN

Server:         192.168.100.2
Address:        192.168.100.2#53

Name:   pi.hole
Address: 192.168.100.2
Name:   pi.hole
Address: fdec:4d47:b3ab:b100:f746:bc86:40d9:81f9

Server:         192.168.100.2
Address:        192.168.100.2#53

Non-authoritative answer:
Name:   google.com
Address: 172.217.28.14
Name:   google.com
Address: 2800:3f0:4001:810::200e

Server:         192.168.100.2
Address:        192.168.100.2#53

Name:   kos.lan
Address: 192.168.100.38

This machine where I disable IPv6 is configured like this now:

pi@netpink:~ $ cat /etc/resolv.conf
# Generated by resolvconf
domain lan
nameserver 192.168.100.2
pi@netpink:~ $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 00:23:5a:f2:96:a5 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 00:26:5e:49:53:43 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.39/24 brd 192.168.100.255 scope global dynamic noprefixroute wlan0
       valid_lft 3194sec preferred_lft 2744sec
pi@netpink:~ $

fellipec · November 16, 2020, 10:26pm

I think I found the problem and is a really weird one.

I run the script that nslookup'd several times in 3 machines and recorded the screen:

1- Raspberry Pi on wifi
2- Debian machine on wifi
3- Windows machine on wired network

As we can see the machines from Wifi connection don't trigger the same responses in the log of Pi-hole. There is something very wrong there.
Then I went back to the Wireshark capture. The DNS replies it captured, with source address 192.168.100.2, the Pi-Hole IP, have a different MAC address in the Ethernet frame.

Then I checked my ARP table to see who have that MAC address: My Access point (that is not the same device as the internet modem)

For some reason the Access Point is hijacking the DNS queries. Then I checked its configuration and it's set manually to use the same 192.168.100.2 Pi-hole IP.

Not happy with that, I enable its telnet interface and...

admin@RT-AC59U:/tmp/home/root# cat /etc/resolv.conf
nameserver 192.168.100.2
nameserver 192.168.100.1

The 192.168.100.1 is the fiber modem. I can't disable it's DNS server (the ISP locks that config) It's DHCP server is down (that the ISP didn't lock) and I use Pi-Hole's own DHCP. But for some reason I have no idea, the Access point set itself to use that IP to.

Now it's narrowed down to the access point. Dan, I wish to thank you A LOT for helping me figure this out. Thanks very much for your time!

@DanSchaper : Turned out that the router i bought last week, when configured as wifi access point ommit several itens in the config page. Configured it as a router (don't matter because in Pi-Hole I use the modem as gateway anyways) and it them show me a firewall config that was enable by default. I disabled all that features and now all work as intended.

system · December 7, 2020, 10:26pm

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