Pihole DNS

[Mr. Boniato]

hmm.. do you mean like this?
I tried it this way and it works fine for me, but I am not sure if it's correct or not.
I am using Pihole's GUI to select the Upstream, because that's what you use when setting up Pihole.

View attachment 46275

View attachment 46276

View attachment 46274

yes that is how I have it, but I use clean browsing instead of open dns.

 

[Tech9]

Add CleanBrowsing addresses to Custom 1 and Custom 2, if not available in pre-selected servers already. Uncheck everything else to use CleanBrowsing only. You guys really need to read more about Pi-hole uses and configuration. This looks like random clicking and trying if you still have Internet.

 

[SomeWhereOverTheRainBow]

Add CleanBrowsing addresses to Custom 1 and Custom 2, if not available in pre-selected servers already. Uncheck everything else to use CleanBrowsing only. You guys really need to read more about Pi-hole uses and configuration. This looks like random clicking and trying if you still have Internet.

I can list a few methods to configure pihole and the router. There are atleast 3 or 4 different methods I have used in the past that have all worked well. But now I have by far the cleanest method, but most people new to this get easily confused so I try not to share to prevent the onset of confusion. @bennor Typically has the atypical recommended method that piholes site recommends as the "default" method over LAN DNS, it works well but can have leaks with devices that don't accept the dhcp configuration advertised by the router. Then users have to resort to using the firewall to force clients to use pihole, those requests appear as though they are "the router" as the client.

 

[Mr. Boniato]

Can you be so kind to explain what is difference of adding the dns sever in custom 1..2 or just having 192.168.1.1 which is telling pihole to use the same upstream dns server?

 

[SomeWhereOverTheRainBow]

Can you be so kind to explain what is difference of adding the dns sever in custom 1..2 or just having 192.168.1.1 which is telling pihole to use the same upstream dns server?

Pass.

 

[Mr. Boniato]

I saw a comment from Merlin https://www.snbforums.com/threads/pihole-dns-server.82129/post-806428
he say there:

If you want to cover the whole LAN:

1) WAN set to ISP DNS - - - different with me is i use clean browsing, not isp
2) PiHole upstream DNS set to router IP <------ HERE
3) DNS Director set to force the use of the PiHole IP (per client or globally), or LAN DNS set to PiHole IP

this is how mine is set. are you saying this is wrong?

 

[SomeWhereOverTheRainBow]

I saw a comment from Merlin https://www.snbforums.com/threads/pihole-dns-server.82129/post-806428
he say there:

If you want to cover the whole LAN:

1) WAN set to ISP DNS - - - different with me is i use clean browsing, not isp
2) PiHole upstream DNS set to router IP <------ HERE
3) DNS Director set to force the use of the PiHole IP (per client or globally), or LAN DNS set to PiHole IP

this is how mine is set. are you saying this is wrong?

I wouldn't say it is wrong; however, it is one way it can be configured. All request that get sent via DNS Director will have no client information. They will appear as though the router made the request. If you are fine with that, feel free to go on your merry way.

 

[jata]

Not sure how helpful this is but I have my setup as follows:

• Primary DNS: RPI running dietpi with adguard home and unbound setup (mainly automatically configured/setup managed)
• Secondary DNS: NextDNS on a their free service (<300k lookups/mth i think) - this is used to catch stuff that does go through primary (e.g. if i need to reboot primary). Also allows me to use nextDNS app to block ads on my iphone when off the LAN
• WAN DNS: set to google DNS or my ISP (don't care really as not really used - only by router f/w stuff)
• DHCP DNS: set to primary and secondary as outlined above. All clients using DHCP...
• DNS Director: Off (not needed for me. I have local client name lookup/resolution by adding the following to unbound config) - [//50.168.192.in-addr.arpa/lan/local/]192.168.50.1:53

 

[SomeWhereOverTheRainBow]

I saw a comment from Merlin https://www.snbforums.com/threads/pihole-dns-server.82129/post-806428
he say there:

If you want to cover the whole LAN:

1) WAN set to ISP DNS - - - different with me is i use clean browsing, not isp
2) PiHole upstream DNS set to router IP <------ HERE
3) DNS Director set to force the use of the PiHole IP (per client or globally), or LAN DNS set to PiHole IP

this is how mine is set. are you saying this is wrong?

Here is my method

Post in thread 'Pihole DNS Server' https://www.snbforums.com/threads/pihole-dns-server.82129/post-806485

 

[Mr. Boniato]

I wouldn't say it is wrong; however, it is one way it can be configured. All request that get sent via DNS Director will have no client information. They will appear as though the router made the request. If you are fine with that, feel free to go on your merry way.

ok. at least I feel good to know the way I have it is not incorrect, specially if Merlin say to use it
I knew was correct way just not sure what was the difference comparing both ways.

thank you for helping.

 

[SomeWhereOverTheRainBow]

ok. at least I feel good to know the way I have it is not incorrect, specially if Merlin say to use it
I knew was correct way just not sure what was the difference comparing both ways.

thank you for helping.

It is the most preferred method since most people don't feel comfortable using custom scripts and having a simple webui method makes it easy to explain.