Running IPv4 but still getting some adds over IPv6

Help
1

Running the latest version on raspberry pi zero W, DNS over https with Cloudflare. Use Scott Helme's setup. Using dnsmasq not FTL. IPv4 network, IPv6 blocked in the router and ISP doesn't support it. IPv6 test says:
IPv6 connectivity: IPv6 Not supported
Browser
Default IPv4
Fallback No
DNS
DNS4 + IP6 Unreachable
DNS6 + IP4 Reachable
DNS6 + IP6 Unreachable

Noticed some adds are still going through, checked the queries, noticed known add server blocked over IPv4 but forwarded over IPv6. Manually blacklisted the server on IPv6, refreshed the webpage, add is gone. Found a thread about it but it was about FTL not dnsmasq so it doesn't seem to apply to my setup.

Pi-hole version is v3.3.1 (Latest: v3.3.1)
AdminLTE version is v3.3 (Latest: v3.3)
FTL version is v3.0 (Latest: v3.0)

dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2018-04-23 19:39:17 UTC; 2min 56s ago

sudo systemctl status pinhole-FTL
Unit pinhole-FTL.service could not be found.

2

sudo systemctl status pinhole-FTL try pihole-FTL and see if that gives you a response, not pinhole-FTL.

Also, see Why do blacklisted domains show IPv4 as "Pi-holed" but not IPv6 in the query log?

3

sudo systemctl status pinhole-FTL
Unit pinhole-FTL.service could not be found.

4

Yes, the proper command should be sudo systemctl status pihole-FTL. Your command is for pinhole-FTL and that's not a service that exists.

5

Damn, you're right. Sorry.

root@raspberrypi:~# sudo systemctl status pihole-FTL
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Tue 2018-04-24 00:55:17 UTC; 6min ago
Docs: man:systemd-sysv-generator(8)
Process: 4761 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=1/FAILURE)
Process: 4799 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/pihole-FTL.service

Apr 24 00:55:16 raspberrypi systemd[1]: Starting LSB: pihole-FTL daemon...
Apr 24 00:55:17 raspberrypi pihole-FTL[4799]: Not running
Apr 24 00:55:17 raspberrypi pihole-FTL[4799]: rm: cannot remove '/var/run/pihole/FTL.sock': No such file or d
Apr 24 00:55:17 raspberrypi su[4818]: Successful su for pihole by root
Apr 24 00:55:17 raspberrypi su[4818]: + ??? root:pihole
Apr 24 00:55:17 raspberrypi su[4818]: pam_unix(su:session): session opened for user pihole by (uid=0)
Apr 24 00:55:17 raspberrypi pihole-FTL[4799]: FTL started!
Apr 24 00:55:17 raspberrypi systemd[1]: Started LSB: pihole-FTL daemon.

6

And then check the link I provided for the explanation of why you will see IPv6 forwarded when you do not have IPv6 capability on the network segment. It's a false positive, since there's no way for an IPv6 address to be reached from inside your network.

7

Checked the link and added the pihole-FTL.conf file after noticing the add problem.

RESOLVE_IPV6=no
AAAA_QUERY_ANALYSIS=no

just restarted the FTL service

root@raspberrypi:/etc/pihole# sudo systemctl status pihole-FTL
● pihole-FTL.service - LSB: pihole-FTL daemon
Loaded: loaded (/etc/init.d/pihole-FTL; generated; vendor preset: enabled)
Active: active (exited) since Tue 2018-04-24 01:13:27 UTC; 4s ago
Docs: man:systemd-sysv-generator(8)
Process: 7630 ExecStop=/etc/init.d/pihole-FTL stop (code=exited, status=0/SUCCESS)
Process: 7652 ExecStart=/etc/init.d/pihole-FTL start (code=exited, status=0/SUCCESS)

8

It will show exited status when it forks the process. Can you do a pihole -d to check the configuration and upload the logs for us to look over? You'll get a token that lets us know which log to take a look at.

9

token is gs5wyuolye.

Many thanks!

11

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