DNS in a Mess - vr600 & Pihole

[#1]

Hi everyone

Thanks for reading this post, so I seem to be in a strange loop i can't seem to fix but things appear to be working?

I have an Archer Vr600 connected to a Raspi running pihole. 

I log into the routers settings - Under Advanced setting -The Archer's dns is pointed to the pihole (static IP), however on the Basic settings screen of the Archer it says dns server 212.159.6.10 212.159.6.9 which is plus net.

The pihole is set to cloudflare however that according to 1.1.1.1 help, it is not connected to them but Google, it did say worldstream earlier before I reset the pihole.

I'm trying to get everything to say 1.1.1.1

any help is appreciated

)

[#2]

@largepie88 welcome to the forum.

If I recall the basic network map displays the plusnet dns hosts which is populated by the broadband user logging on.

You would set up the pihole IP Address in Advanced >Network >LAN settings. Set the Primary DNS to be the pihole IP.

BTW best you give the pihole a static IP.

If you perform a nslookup on flurry.com it should report 

nslookup flurry.com
Server: 127.0.0.53
Address: 127.0.0.53#53

Non-authoritative answer:
Name: flurry.com
Address: 0.0.0.0
Name: flurry.com
Address: ::

If the pihole dns is being used

HTH

[#3]

To add,

As the VR600 is acting as the DNS server then all devices on your network would display the DNS host IP being the same as the default gateway and VR600

[#4]

nslookup flurry.com

server 8.8.8.8

address 8.8.8.8#53

non authoritative answer 

name flurry.com

address 212.82.100.150

name flurry.com

address 98.136.103.23

name flurry.com

address 74.6.136.150

is what i get when doing the look up.

the pi hole is on a static ip and primary and secondary dns on the router. The pihole dns is set for cloudflare.

All the 8's is google? Is something not working?

thanks for the help it is extremly appreciated.

[#5]

Hi, to me from that reply from a nslookup suggests the device is setup to use google and not the pihole dns

using router for dns (plusnet dns)

pi@dan:~ $ nslookup flurry.com 

Server: 192.168.10.1
Address: 192.168.10.1#53

Non-authoritative answer:
Name: flurry.com
Address: 212.82.100.150
Name: flurry.com
Address: 98.136.103.23
Name: flurry.com
Address: 74.6.136.150

If I force the nslookup request to use the pihole DNS I see

pi@dan:~ $ nslookup flurry.com 192.168.10.252     <--- my pihole IP
Server: 192.168.10.252
Address: 192.168.10.252#53

Name: flurry.com
Address: 0.0.0.0
Name: flurry.com
Address: ::

for linux cat /etc/resolv.conf should detail how DNS is set.

for windows ipconfig /all | find "DNS Servers"

HTH

[#6]

Hi

I've got a feeling a format of the OS and the pi software maybe incoming.

I've tried everything, repair, reconfigure,restart dns and Im stuck on googles dns. even tried enabling and disabling dchp.

The router is talking to the pi and the pi is blocking as there is activity from everything that is connected looking at the logs, but am unable to shift the dns on the pi to something else.

even gone through the debug for anything interesting, and nothing even tried using OpenNIC dns in the custom.... and stuck on google

Things sort of went wrong after a week of spotty internet as there was a problem with a connection on the telegrah pole, as the router connection dropped every 15 mins- current speed is 7mb, used to be 15mb, before that happened, even though its been repaired!. Though I did have a lighttpd problem last month after the last but one update. So probably best off with a full reset and reboot of router, os and pihole tomorrow.

thank you for help

[#7]

https://pimylifeup.com/raspberry-pi-dns-settings/

This fixed it! I have not a  clue why, but its going to 1.1.1.1 

Server: 1.1.1.1
Address: 1.1.1.1#53

Non-authoritative answer:
Name: flurry.com
Address: 98.136.103.23
Name: flurry.com
Address: 74.6.136.150
Name: flurry.com
Address: 212.82.100.150

hopefully all good.  Thank you once again

[#8]

@largepie88 

not sure what you have fixed?

pi-hole is an application which has both a DNS client and DNS server, the pi-hole software ignores the host computer (raspberry pi) DNS setting it is installed on. The pi-hole DNS client is setup during the install and can be changed in the web GUI.

The DNS client connects to your preferred public DNS hosts, in your case you've chosen cloudflare. The pi-hole application uses this DNS host to apply the host filtering.

The DNS server the pi-hole runs creates a DNS service for your LAN on the IP Address of the host running the pi-hole application, it is this address all devices on your LAN should use as the DNS IP Address.When you perform a nslookup on a host using the pi-hole DNS the Server IP Address should be that of the pi-hole NOT cloudflare.

This example below the server IP 192.168.10.252 is my raspberry pi running pi-hole.

nslookup plus.net
Server: 192.168.10.252
Address: 192.168.10.252#53

Non-authoritative answer:
Name: plus.net
Address: 212.159.8.2
Name: plus.net
Address: 212.159.9.2

nslookup flurry.com is used to test the pi-hole DNS is actually working, the return IP address of 0.0.0.0 show flurry.com is blocked.

nslookup flurry.com
Server: 192.168.10.252
Address: 192.168.10.252#53

Name: flurry.com
Address: 0.0.0.0
Name: flurry.com

This example below show nslookup on a device not using the pi-hole DNS, 192.168.10.1 is my HUB Two 

nslookup flurry.com
Server: 192.168.10.1
Address: 192.168.10.1#53

For you VR600 in Advanced >Network >LAN settings you should make the Primary DNS to be the IP Address of your pi-hole, the Secondary DNS does not need changing. 

Hope this makes sense?