Question pihole setup/config questions

[chenks]

You don't have to mention the port in windows. Just ip is enough.

nope, the IP alone isn't enough, as when i set my DNS on the laptop to 192.168.1.2 it couldn't resolve anything.

 

[chenks]

i guess there is no way to end up with the docker instance having it's own IP address in the 192.168.1.x range?

 

[Geeked]

I made this guide on how I installed it here Block Ads on your Network with Pi-Hole Hosted on Synology - NAS Hosted

It's a very dumbed down guide where I basically hold your hand step by step

 

[chenks]

I made this guide on how I installed it here Block Ads on your Network with Pi-Hole Hosted on Synology - NAS Hosted

It's a very dumbed down guide where I basically hold your hand step by step

that's exactly how i have it set up.
but when i enter the IP of the NAS as the DNS server on my laptop it fails to resolve any domain names.

 

[Geeked]

Can you show me a screenshot of how you are adding the IP on your laptop? I want to make sure everything is correct. Also make sure you reserve the NAS IP on your router so it doesn't change randomly. Thanks.

 

[chenks]

yes my NAS has a static IP
and i'm just changing the DNS server from automatic to manually assigned and using 192.168.1.2 (the NAS IP).
i'm doing that the correct way as i previously had pihole set up in bridge mode before removing and creating it again.

 

[Geeked]

If you'd like, I can TV into your NAS and look at it?

 

[chenks]

sorry, not an option.
but i am happy to provide other data if required

 

[chenks]

this is what happens when i set the DNS server as 192.168.1.2 on the laptop

Wireless LAN adapter WiFi:

   Connection-specific DNS Suffix  . : localdomain
   Description . . . . . . . . . . . : Killer Wireless-n/a/ac 1535 Wireless Network Adapter
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::99b5:ffbf:42fb:c149%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.84(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 10 April 2020 07:31:56
   Lease Expires . . . . . . . . . . : 11 April 2020 20:04:45
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 127710928
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-84-17-A9-9C-B6-D0-F1-C6-BF
   DNS Servers . . . . . . . . . . . : 192.168.1.2
   NetBIOS over Tcpip. . . . . . . . : Enabled

C:\Users\chenk>nslookup google.com
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  192.168.1.2

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

 

[chenks]

and this is it set back to the original DNS

Wireless LAN adapter WiFi:

   Connection-specific DNS Suffix  . : localdomain
   Description . . . . . . . . . . . : Killer Wireless-n/a/ac 1535 Wireless Network Adapter
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::99b5:ffbf:42fb:c149%14(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.84(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : 10 April 2020 07:31:57
   Lease Expires . . . . . . . . . . : 11 April 2020 20:05:51
   Default Gateway . . . . . . . . . : 192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 127710928
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-84-17-A9-9C-B6-D0-F1-C6-BF
   DNS Servers . . . . . . . . . . . : 192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

C:\Users\chenk>nslookup google.com
Server:  unifi.localdomain
Address:  192.168.1.1

Non-authoritative answer:
Name:    google.com
Addresses:  2a00:1450:4009:819::200e
          216.58.211.174

 

[jphermans]

And what have you set as DNS in your pihole settings ? The standard Google DNS 8.8.8.8?

 

[chenks]

yes, that's correct.
i deleted the container and set it up again following your site instructions to the letter, same end result

 

[jphermans]

And there is no collision ip conflict with another device? Change the IP address to x.x.x.254 and test it again.

 

[chenks]

change what IP address to .254?

the IP address of 192.168.1.2 is the IP of the NAS which the docker is running on.
it's a static IP (via DHCP reservation), and the NAS runs many other dockers and services just fine. if you mean change the IP of the NAS then that is just not possible as it would break other services.

Here is the docker settings json export

 

[jphermans]

If you work with macvlan then you can use another IP address. Maybe you can try that. I have many containers running with macvlan network mode.

 

[chenks]

but your method should work though?
so why isn't it working for me.

personally i'm a little confused as to how this method could ever work, as DNS uses port 53 and at no point has the NAS been set to accept connections on port 53 using this method.

 

[jphermans]

I should work yes, have two nasses and both have installed Adguard (but works also with pihole) and no problem with it.

 

[chenks]

but the NAS isn't listenting on port 53, so it won't work.

 

[chenks]

however doing a port check, the NAS is saying port 53 is open, however it suggest that traffic on port 53 is not being received into the pihole docker container

PS C:\Users\chenk> tnc 192.168.1.2 -port 53                                                                                                                                                                                                                                                                                                  ComputerName     : 192.168.1.2
RemoteAddress    : 192.168.1.2
RemotePort       : 53
InterfaceAlias   : WiFi
SourceAddress    : 192.168.1.84
TcpTestSucceeded : True

 

[itsjasper]

Just a thought - in the docker config, are you mapping the UDP & TCP ports 53 in the container to 53, or are they set to auto?

As you are running in host mode, you'd need to have them set to 53:53, not Auto:53 as well as to not be running Synology DNS Server (or anything else on the same port). ;-)