Been having a couple problems on "Installation Complete" and DNS

[Jonny]

cvh0rcuksi

[DanSchaper]

Thanks, and what DNS servers are listed for the client? Only the Pi-hole IP address or do you have other DNS servers listed on the client?

[Jonny]

I'm sorry, I don't quite understand. Where do I go to check that?

[DanSchaper]

ipconfig /all and look at the IP addresses for the DNS server.

[Jonny]

I only have the Pi-hole servers adresses.

[DanSchaper]

Okay, on the Pi-hole device run pihole -t and this will start tailing the query log. If you see entries scroll when you browse with a client check to see if they are blocking. If you don't see entries scroll then your clients are not using the Pi-hole for their DNS. Also check the web admin interface under the Query Log page and see if there are green and red entries displayed.

[Jonny]

On the Pi-hole device, the entries do not scroll. On the Pi-hole Query Log there are some entries that are red and green.

[DanSchaper]

If the log is not scrolling then your clients are not querying the Pi-hole for the DNS. And that's what I suspected as the debug log did not show any entries in the portion that captures the query log. How many pages are on the web interface? One or two or more than that?

[Jonny]

I moved the Raspberry Pi to the router and used an Ethernet cable. On the Query Log it shows a couple entries, almost all green.

[DanSchaper]

Do you see the IP addresses of the clients being displayed in any of the graphs? And are the counters increasing in the Total Queries when you browse sites with the client?

[Jonny]

I have three clients showing in the second graph. The total query number isnt rising.

[DanSchaper]

Can you go to your client and copy the output from ipconfig /all so we can see what is set there?

[Jonny]

`Windows IP Configuration

Host Name . . . . . . . . . . . . : Sharp
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : attlocal.net

Wireless LAN adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 1E-3E-84-75-E7-74
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : attlocal.net
Description . . . . . . . . . . . : Broadcom NetLink (TM) Gigabit Ethernet
Physical Address. . . . . . . . . : 20-89-84-6D-D7-35
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : attlocal.net
Description . . . . . . . . . . . : Qualcomm Atheros AR5B125 Wireless Network
Adapter
Physical Address. . . . . . . . . : 1C-3E-84-75-E7-74
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2600:1700:16e0:b6d0::51e(Preferred)
Lease Obtained. . . . . . . . . . : Monday, July 2, 2018 1:54:14 PM
Lease Expires . . . . . . . . . . : Wednesday, August 1, 2018 1:54:14 PM
IPv6 Address. . . . . . . . . . . : 2600:1700:16e0:b6d0:8967:e7b3:ae19:815(Preferred)
Temporary IPv6 Address. . . . . . : 2600:1700:16e0:b6d0:f7:497:6db5:bfb5(Deprecated)
Temporary IPv6 Address. . . . . . : 2600:1700:16e0:b6d0:479:4cb7:c4a1:8b76(Preferred)
Temporary IPv6 Address. . . . . . : 2600:1700:16e0:b6d0:5573:a70a:a53b:f11c(Deprecated)
Temporary IPv6 Address. . . . . . : 2600:1700:16e0:b6d0:98c5:9215:7053:7a8(Deprecated)
Link-local IPv6 Address . . . . . : fe80::8967:e7b3:ae19:815%3(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.73(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Monday, July 2, 2018 7:15:36 AM
Lease Expires . . . . . . . . . . : Wednesday, July 4, 2018 7:04:00 PM

Default Gateway . . . . . . . . . : fe80::d6b2:7aff:fe47:5be5%3 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 354172548
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-01-76-12-20-89-84-6D-D7-35

DNS Servers . . . . . . . . . . . : 2600:1700:16e0:b6d0::1
192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 13:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:c669:fe82:1c15:3028:3f57:feb6(Preferred)
Link-local IPv6 Address . . . . . : fe80::1c15:3028:3f57:feb6%8(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 134217728
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-01-76-12-20-89-84-6D-D7-35

NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.attlocal.net:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : attlocal.net
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

[DanSchaper]

@Jonny

2600:1700:16e0:b6d0::1

That IP address is not the Pi-hole address. Looks like that is the IPv6 address of the router. That is how the client is resolving names without querying the Pi-hole.

[DanSchaper]

You said you changed the network connection of the Pi-hole? Can you run a new pihole -d so that we can see the new configuration?

[Jonny]

hj2l908cci

Do i run the curl -sSL https://install.pi-hole.net | bash to change the Lan to Ethernet? And should I disable IPv6 if I configure?

[Jonny]

Ok, some of the ads that are sent through on websites are getting blocked, but some are getting through. Is this because of the IPv6? Or is it some other thing that is allowing them through?

[DanSchaper]

Yes, if the client has the option to use another DNS server, like the IPv6 router, it will use that and will leak advertisements. Take a look at the following threads for some information on how to work around that.

Use IPv6 ULA addresses for Pi-hole

Many users have reported that frequently changing IPv6 addresses cause page load to be slow or even prevent from working at all. The issues can be fixed by updating the IPv6 address in /etc/pihole/setupVars.conf followed by a run of pihole -g. However, this solution turns out to be very inconvenient since it might be necessary to change the IPv6 address on a regular basis (maybe even multiple times a day). An alternative approach we are currently looking into is the usage of ULA addresses which…

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

This behavior can be fixed by setting AAAA_QUERY_ANALYSIS=no in /etc/pihole/pihole-FTL.conf (you need to create this file if it doesn't exist). If you still see blacklisted IPv6 domains show as forwarded in your query log but don't have IPv6 enabled, you may see a false positive like the image below, where the IPv4 version of the domain is blocked, but not the IPv6 version. root@pihole:~ $ cat /etc/pihole/gravity.list | grep edge.quantserve.com 192.168.1.126 edge.quantserve.com [image] I…

Why Some Pages Load Slow When Using Pi-hole And How To Fix It (for versions < v4.0)

Originally published at: https://pi-hole.net/2018/02/02/why-some-pages-load-slow-when-using-pi-hole-and-how-to-fix-it/ Update: 2018-08-06 As of v4.0, this should no longer be a problem unless you choose to deviate from the new default blocking mode and return to the IP-based mode. Update: 2018-05-26 This problem is far less likely to happen when using NXDOMAIN or NULL blocking: https://pi-hole.net/2018/05/18/nxdomain-and-null-blocking-with-ftldns/ Pi-hole can make your network run…

[Jonny]

I can see that the IPv6 is letting ads through, but when I check my Queries, it shows two of the same ads- one on IPv4 and one on IPv6. Both are letting them through and blocking them, instead of IPv4 only blocking and IPv6 only letting through. And when I put /etc/pihole/setupVars.conf I get bash: /etc/pihole/setupVars.conf: Permission denied Upon reading the second post you showed, it says to make a file for that command. How would I do that?