Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DHCP Synology, PiHole Docker and port 53... #267

Closed
silversegarra opened this issue Apr 26, 2018 · 12 comments
Closed

DHCP Synology, PiHole Docker and port 53... #267

silversegarra opened this issue Apr 26, 2018 · 12 comments
Labels

Comments

@silversegarra
Copy link

Hello, I've Synology in the last vesion, PiHole Docker in last version too...

  • DHCP in Synology

Like I've port 53 in use with DHCP Server in Synoogy, PiHole can't start. I've installed with HOST option, and I'm able to change 80 port, by 8888, with WEB_PORT variable, then isn't a problem, but I don't know how to change, and if it's possible to change port 53.

Anyone, could help me?

Thanks

@diginc
Copy link
Collaborator

diginc commented Apr 26, 2018

DHCP is port 67, DNS is port 53...do you mean DNS? Sounds like a port conflict with synology's built in DNS server. You should be able to google how to disable synology's DNS server so you can run your own in docker without ports conflicting. As of right now the port 53 is not customizable.

Please provide your docker run command and the error it provides so I can better understand your problem...

@silversegarra
Copy link
Author

Thanks, that's right... port 53 is in use by Synology, I'll try to find, how disable it un Synology, thanks

@longstone
Copy link

longstone commented Apr 26, 2018

You should disable synology DNS if in use...

@silversegarra
Copy link
Author

Ok, but I prefer Synology DNS, if I can have both, I'll try Pi-Hole in Raspberry... :) Thanks

@nxadm
Copy link
Contributor

nxadm commented May 1, 2018

@silversegarra you could check the documentation/google to check if you can add a 2nd IP to the NAS. I don't know if it's possible (I don't own a Synology NAS), but being UNIX underneath it should.

@silversegarra
Copy link
Author

I can add two IPs, but the problem is the port...

@nxadm
Copy link
Contributor

nxadm commented May 2, 2018

@silversegarra Actually, no. You can have 2 ip's with the same port. DNS does not broadcast, it just a service.

@ordimans
Copy link

dnsmasq is running on same port, if you enable DHCP server on Synology.
Even if DNS Server is not installed, DHCP server required DNS.
SO no solution ?

@diginc
Copy link
Collaborator

diginc commented Feb 20, 2020

Docker macvlan networking is a great way to get a 2nd Host LAN IP (as opposed to docker network) allocated to your docker host to completely avoid the host's ports / avoid port conflicts

@ordimans
Copy link

ordimans commented Mar 4, 2020

Docker macvlan networking is a great way to get a 2nd Host LAN IP (as opposed to docker network) allocated to your docker host to completely avoid the host's ports / avoid port conflicts

Thanks, it worked perfectly.
I just had a last problem with Conditional Forwarding...; It doesn't work.
I enable the option, and put the IP of Synology (with DHCP) and local.home in domain, but adress was not resolved.

@jjpeet
Copy link

jjpeet commented Feb 18, 2021

Hi @diginc I've run into the same issue, and would like to configure Docker mtacvlan as you suggest. But I'm not sure where to start. Is it network setting within the docker app on the Synology where I should be looking?
Thx
JP

@buckaroogeek
Copy link

buckaroogeek commented Feb 18, 2021

I have example docker-compose file which sets up a pihole (and other services) on a docker macvlan at https://github.com/buckaroogeek/unifi-pihole-doh-docker/blob/master/docker-compose.yaml. In the same repo is a scripts/shim.sh file which configures the necessary synology macvlan so that you can ping the pihole ip from the synology ip.

The readme in the repo goes into more detail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

8 participants