Pi-hole

[jphermans]

Has anyone pi-hole run with macvlan driver? I Am using this tutorial, but this seems not to work very well. It always restarts the container. Maybe there's another way to let it work flawlessly in Synology docker.

 

[Rusty]

I'm running it in docker on 'bridge'. But I have no need for dsm dns or dhcp so port 53 is open for me. Running with no problems.

 

[daptap]

I'm running it in docker on 'bridge'. But I have no need for dsm dns or dhcp so port 53 is open for me. Running with no problems.

Did you use a certain tutorial to get this working?

 

[Rusty]

No, nothing special. Just make sure that there is no other service (in docker or DSM) thats using tcp or udp port 53 and make sure that when you map your container ports that you map 53 to 53 only. The reason is that you can't change DNS port number on your client-side, so mapping it to a custom port will not make it work as intended.

Regarding environment variables you only need ServerIP variable with the value of your Syno NAS IP, considering that after you get it up and running you will be using that IP address as a DNS IP for your lan clients.

 

[daptap]

@Rusty - when i set it up it did not have me map ports since i chose “use same network as docker host” (ports tab is blocked when this option chosen). But i don’t think i have ports conflict (not running much).

I used . This guide. Main thing i changed was web_port set to 8181 and not 8080 since i believe unifi controller docker uses that.

my main question at this point is what values do you put in srm, network center, local dns and internet dns? Is it necessary to point those to my new pihole (which for me is same lan ip as my nas)?

 

[Rusty]

when i set it up it did not have me map ports since i chose “use same network as docker host” (ports tab is blocked when this option chosen). But i don’t think i have ports conflict (not running much).

ofc in that case you can't map them, but if the container is running there are def no conflicts.

my main question at this point is what values do you put in srm, network center, local dns and internet dns? Is it necessary to point those to my new pihole (which for me is same lan ip as my nas)?

Well I have it setup like this. I use my NAS IP address (thats running pihole) and add it to my clients network settings DNS field. If you want you can do that on the router level as well, but I place it on the client end considering that I want to have the option if some clients need to use specific DNS settings apart from pihole/router etc.

The point is, after you set ip up, configure it as a primary DNS on the device of your choice (clinet or router, it will depend on your needs).

 

[daptap]

ofc in that case you can't map them, but if the container is running there are def no conflicts.


Well I have it setup like this. I use my NAS IP address (thats running pihole) and add it to my clients network settings DNS field. If you want you can do that on the router level as well, but I place it on the client end considering that I want to have the option if some clients need to use specific DNS settings apart from pihole/router etc.

The point is, after you set ip up, configure it as a primary DNS on the device of your choice (clinet or router, it will depend on your needs).

I’d like to do it on the router but have seen conflicting advice on where to change the dns: (1) local setting, (2) network settings, and (3) both. What is your best guess? I’ve been trying test but still confused ( doesn’t help that my pihole console log shows times that are way off!)

 

[Rusty]

In this case you want local setting. Network settings I'm guessing you mean the one under "Internet" section? If so don't change that. pi hole is for local request to be filtered before the final request goes to the internet.

 

[daptap]

In this case you want local setting. Network settings I'm guessing you mean the one under "Internet" section? If so don't change that. pi hole is for local request to be filtered before the final request goes to the internet.

Yes, meant “internet” section. Thanks!
So, in Network Center > Local Network, DHCP Server, Primary DNS -- I would put "192.168.1.8", the IP address of my NAS and my PiHole, correct? Would I also put it in Guest DNS Server?

One thing that confuses me: so, the PiHole console also has a DNS section where you can choose cloudflare, google, etc. How does that work with the router "Internet" section where you can choose upstream DNS as well? Does it cause conflicts? Am I running two DNS servers?

Also, do I need to port forward on the router since my pihole is at 192.168.1.8:8181?

Sorry for these ignorant questions.

 

[Rusty]

I would put "192.168.1.8", the IP address of my NAS and my PiHole, correct?

correct

Would I also put it in Guest DNS Server?

If you want to, yes.

Also, do I need to port forward on the router since my pihole is at 192.168.1.8:8181?

Not unless you wanna access the UI via the Internet

How does that work with the router "Internet" section where you can choose upstream DNS as well?

All clients in your LAN that will have the DNS parameter towards your pihole will end up on the internet via upstream DNS settings in your pihole configuration. All clients that will not have pihole as dns will end up on the router and its DNS servers.

In your case traffic will go like this:

client > router (with DNS towards pihole) > pihole > DNS that you configure in the upstream settings > Internet

So, no, you will not have any conflicts considering that in your LAN you have only one DNS "server", that's pihole. Router DNS settings are just parameters that point to a specific DNS server, not the server role, so again, no conflicts.

 

[daptap]

@Rusty - thank you very much.