Yes, it seems to be only IPv4. No options within the router UI to configure IPv6 also it seems. However I believe previous versions of the router software did allow some IPv6 options.
Yes, ping 8.8.8.8 works even when nslookup doesn't. I tried this will the multiple DNS IPs listed below and it is the same with all.
If I'm reading it correctly, it looks like there might be some block on the DNS/port 53.
So ping to 8.8.8.8 gave the the following
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=17ms TTL=117
Reply from 8.8.8.8: bytes=32 time=8ms TTL=117
Reply from 8.8.8.8: bytes=32 time=9ms TTL=117
Reply from 8.8.8.8: bytes=32 time=8ms TTL=117
Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 17ms, Average = 10ms
nslookup flurry.com 8.8.8.8 gave the following
Server: dns.google
Address: 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to dns.google timed-out
Ping to 9.9.9.9 gave similar to 8.8.8.8 above.
nslookup flurry.com 9.9.9.9 gave similar enough to 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 9.9.9.9
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
However, if I set my DNS settings back to the vodafone router's default settings then nslookup flurry.com 8.8.8.8 gives the following result.
Server: dns.google
Address: 8.8.8.8
Non-authoritative answer:
Name: flurry.com
Addresses: 74.6.136.150
98.136.103.23
212.82.100.150
And nslookup flurry.com 9.9.9.9 using router defaults gives.
Server: dns9.quad9.net
Address: 9.9.9.9
Non-authoritative answer:
Name: flurry.com
Addresses: 74.6.136.150
212.82.100.150
98.136.103.23
If I'm not mistaken the above two tests indicate that the ISP is not blocking the public DNS in their network. Not sure if this actually helps or provides more confusion at this point.
There is no dedicated firewall equipment on the network. Router firewall services have been tested in the on and off state, as have the client antivirus firewall services. Same result in all cases whether these firewall services are on or off. However there is other equipment that may be interfering that I need to investigate based on the above result that indicates that the ISP is not blocking the public DNS.
There is a powerline adapter to provide stable hard line connection from router location on ground floor to office on third floor. There is a wifi booster also to boost coverage to third floor.
By way of initial test I connected a laptop directly to the vodafone router via ethernet. I set router to point at Pi-hole and ran nslookup tests as per below. ipconfig/all still shows vodafone router distributing itself as a DNS along with Pi-hole in the other two slots.
nslookup flurry.com
Server: vodafone.station
Address: 192.168.1.1
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: flurry.com
Addresses: 74.6.136.150
98.136.103.23
212.82.100.150
nslookup flurry.com 8.8.8.8
Server: dns.google
Address: 8.8.8.8
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: flurry.com
Addresses: 74.6.136.150
98.136.103.23
212.82.100.150
nslookup flurry.com 9.9.9.9
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 9.9.9.9
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: flurry.com
Addresses: 74.6.136.150
98.136.103.23
212.82.100.150