Expected/Actual Behaviour:
These commands are run from the Pi Hole machine itself:
nslookup google.com
Server: 127.0.0.1
Address: 127.0.0.1#53
Non-authoritative answer:
Name: google.com
Address: 172.217.3.174
nslookup pi.hole
Server: 127.0.0.1
Address: 127.0.0.1#53
Name: pi.hole
Address: 192.168.0.200
I would expect that the nslookup provided an IPv6 address as well.
The machine has an IPv6 address.
ifconfig | grep inet6
(standard input):3: inet6 2604:3d09:6780:110c:2387:18d4:92f6:8f58 prefixlen 64 scopeid 0x0<global>
(standard input):4: inet6 fe80::a24f:9a92:eb94:556f prefixlen 64 scopeid 0x20<link>
(standard input):13: inet6 ::1 prefixlen 128 scopeid 0x10<host>
I have IPv6 connectivity:
ping6 google.com
PING google.com(sea15s11-in-x0e.1e100.net (2607:f8b0:400a:808::200e)) 56 data bytes
64 bytes from sea15s11-in-x0e.1e100.net (2607:f8b0:400a:808::200e): icmp_seq=1 ttl=56 time=34.9 ms
64 bytes from sea15s11-in-x0e.1e100.net (2607:f8b0:400a:808::200e): icmp_seq=2 ttl=56 time=27.3 ms
From a different machine (Windows 10):
PS C:\WINDOWS\system32> nslookup pi.hole
Server: myispdns
Address: mypublicip6
Non-authoritative answer:
Name: pi.hole.myddnsname
Address: mypublicip4
PS C:\WINDOWS\system32> nslookup google.com
Server: myispdns
Address: mypublicip6
Non-authoritative answer:
Name: google.com.myddnsname
Address: mypublicip4
From another Raspberry Pi:
nslookup pi.hole
Server: 192.168.0.200
Address: 192.168.0.200#53
Name: pi.hole
Address: 192.168.0.200
nslookup google.com
Server: 192.168.0.200
Address: 192.168.0.200#53
Non-authoritative answer:
Name: google.com
Address: 216.58.217.46
From my Ubuntu machine:
nslookup google.com
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: google.com
Address: 172.217.14.206
Name: google.com
Address: 2607:f8b0:400a:808::200e
nslookup pi.hole
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: pi.hole
Address: 192.168.0.200
Name: pi.hole
Address: 2604:3d09:677f:d5e6:ee63:1827:6ee9:b8e9
01-pihole.conf:
addn-hosts=/etc/pihole/gravity.list
addn-hosts=/etc/pihole/black.list
addn-hosts=/etc/pihole/local.list
localise-queries
no-resolv
cache-size=10000
log-queries
log-facility=/var/log/pihole.log
local-ttl=2
log-async
# If a DHCP client claims that its name is "wpad", ignore that.
# This fixes a security hole. see CERT Vulnerability VU#598349
dhcp-name-match=set:wpad-ignore,wpad
dhcp-ignore-names=tag:wpad-ignore
server=1.1.1.1
server=1.0.0.1
server=2606:4700:4700::1111
server=2606:4700:4700::1001
domain-needed
bogus-priv
dnssec
trust-anchor=.,19036,8,2,49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5
trust-anchor=.,20326,8,2,E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D
local-service
02-pihole-dhcp.conf:
dhcp-authoritative
dhcp-range=192.168.0.10,192.168.0.190,12h
dhcp-option=option:router,192.168.0.1
dhcp-leasefile=/etc/pihole/dhcp.leases
#quiet-dhcp
domain=ackis.duckdns.org
dhcp-rapid-commit
#quiet-dhcp6
#enable-ra
dhcp-option=option6:dns-server,[::]
dhcp-range=::100,::1ff,constructor:eth0,ra-names,slaac,12h
ra-param=*,0,0
04-pihole-static-dhcp.conf
# DHCP Address Reservations
# PC Address Range: 10 - 20
dhcp-host=78:24:AF:D9:D6:B5,192.168.0.10,john
dhcp-host=78:24:AF:47:7F:73,192.168.0.12,john2
dhcp-host=5C:87:9C:0A:15:13,192.168.0.13,johnwifi
dhcp-host=78:24:af:47:81:71,192.168.0.11,chantelle
# Ad hoc DHCP Range: 21-40
# Routers
# Printers
dhcp-host=2C:9E:FC:5C:A2:A9,192.168.0.101,mf4890
dhcp-host=80:3F:5D:08:E0:2A,192.168.0.102,usbprint
# Media Devices
dhcp-host=00:18:DD:05:31:BA,192.168.0.104,hdhrextend
dhcp-host=9C:AD:EF:60:06:C5,192.168.0.105,obi200
dhcp-host=00:05:cd:90:b4:db,192.168.0.106,denon
# IP Cams
# Monoprice Cam
dhcp-host=00:1B:C7:02:1B:4F,192.168.0.150,ipcam1
dhcp-host=00:1B:C7:FF:D2:79,192.168.0.151,ipcam1wifi
# D-Link Cam - Living Room
dhcp-host=B0:C5:54:14:D4:60,192.168.0.152,ipcam2
#,192.168.0.153,ipcam2wifi
# D-Link Cam - Kitchen
dhcp-host=B0:C5:54:1F:37:DC,192.168.0.154,ipcam3
#dhcp-host=,192.168.0.155,ipcam3wifi
# Servers
dhcp-host=30:9C:23:B6:12:39,192.168.0.199,ubuntu
dhcp-host=b8:27:eb:09:6f:0c,192.168.0.200,dns-pi
dhcp-host=b8:27:eb:7a:de:4b,192.168.0.201,vpn-pi
This file contains various options that the Pi Hole admin console doesn't support that I had enabled in DNSMASQ when I ran it solo.
99-custom-dnsmasq.conf:
# Configuration file for dnsmasq.
# Only queries for private domain are answered by Dnsmasq
local=/dyndns/
local=/.local/
local=//
#listen-address=192.168.0.200
#listen-address=::
# Only listen on the addresses specified with list-address
#bind-interfaces
#no-hosts
dhcp-option=option:dns-server,192.168.0.200
#dhcp-option=option6:dns-server,[::]
dhcp-option=option:ntp-server,192.168.0.199
# Windows/Samba suggestions from default configuration
dhcp-option=option:ip-forward-enable,0
dhcp-option=option:netbios-ns,192.168.0.199
dhcp-option=option:netbios-dd,192.168.0.199
dhcp-option=option:netbios-nodetype,8
dhcp-option=vendor:MSFT,2,1i
#bogus-nxdomain=64.94.110.11
#mx-host=mail.dyndns,30
#txt-record=home.dyndns,"v=spf1 mx -all"
# For debugging purposes, log each DNS query as it passes through
# dnsmasq.
#log-queries
# Log lots of extra information about DHCP transactions.
#log-dhcp
99-custom-server-names.conf
# LAN Name Resolution
address=/.local/192.168.0.199/
address=/.dev/192.168.0.199/
address=/ubuntu/192.168.0.199/
address=/dns-pi/192.168.0.200/
# Web servers
address=/home.dyndns/192.168.0.199
address=/home.local/192.168.0.199
address=/home/192.168.0.199
address=/dyndns/192.168.0.199
# Media Streaming Related
address=/hdhr3.local/192.168.0.103
address=/hdhr3/192.168.0.103
address=/hdhrextend.local/192.168.0.104
address=/hdhrextend/192.168.0.104
address=/obi200.local/192.168.0.105
address=/obi200/192.168.0.105
address=/denon.local/192.168.0.106
address=/denon/192.168.0.106
# LAN Servers
address=/mail.local/192.168.0.199
address=/mail.dyndns/192.168.0.199
address=/mail/192.168.0.199
address=/smtp.local/192.168.0.199
address=/smtp.dyndns/192.168.0.199
address=/smtp/192.168.0.199
address=/pihole.local/192.168.0.200
address=/pihole.dyndns/192.168.0.200
address=/pihole/192.168.0.200
Overall, I have no clue what I'm doing with IPv6 - I'm still in the IPv4 mindset where I need to have a private range to use. I don't know where the raspberry pi got its address from for example, nor if it's a "good" address to have.