Question pihole setup/config questions

Currently reading
Question pihole setup/config questions

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?
 
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.
 
this is what happens when i set the DNS server as 192.168.1.2 on the laptop

Code:
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
 

Attachments

  • Capture.JPG
    Capture.JPG
    50.9 KB · Views: 10
and this is it set back to the original DNS

Code:
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
 
yes, that's correct.
i deleted the container and set it up again following your site instructions to the letter, same end result
 

Attachments

  • Capture.JPG
    Capture.JPG
    46.2 KB · Views: 16
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
 

Attachments

  • pihole-pihole1.zip
    1 KB · Views: 5
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.
 
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

Code:
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
 
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). ;-)
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

Sorry for not replying sooner as I am not getting notification. However, I did manage getting pihole up...
Replies
9
Views
1,772
I'm using adguard/adguardhome and crazymax/unbound. Point Adguard at the unbound box as the upbound server...
Replies
1
Views
2,286
Not sure what's happening but I went drastic. I shut down the PC and did a hard reset of the modem, "enter...
Replies
9
Views
2,003
This indeed is a breaking change. The whole function fix_capabilities() is responsible for the behavior...
Replies
10
Views
2,823
Finally got it dl'd and installed. Had to reconfigure the router.
Replies
4
Views
2,333
I've been running pihole in Docker on my DS920. The only issue I've had is with doing updates. I dl the...
Replies
0
Views
1,791
sorry, was away for a few days. yes, I was talking about the logs that you find in synology. but...
Replies
4
Views
3,986

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top