Selfhosted

60048 readers

1123 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

DNS trouble with pihole running with podman (jlai.lu)

submitted 2 years ago* (last edited 2 years ago) by mat@jlai.lu to c/selfhosted@lemmy.world

12 comments fedilink hide all child comments

Hi people. I am running pihole under podman and its dedicated system account on my NAS. Now, from the NAS, I get a connection refused on ip.of.the.nas:53 but everywhere else in my network, pihole works perfectly. To run pihole as a rootless container, i made it listen on 1053 and I have a firewall redirection from 53 to 1053 for both udp and tcp. Any pointer to where (and how) I can debug this ?

Edit: Small precision about my current setup : ISP router (so I can't really do anything on it) and NAS running opensuse leap

you are viewing a single comment's thread
view the rest of the comments

[–] InnerScientist@lemmy.world 1 points 2 years ago (1 children)

Just set the DNS server to localhost:1053 for the nas?

[–] mat@jlai.lu 1 points 2 years ago (1 children)

Do you have any idea on how to do it ? Knowing that I am on opensuse

[–] InnerScientist@lemmy.world 2 points 2 years ago* (last edited 2 years ago)

Well, on linux I'd use systemd's resolved which would listen on localhost:53 (it would also point resolv.conf there) and then set resolved's uplink server to your custom port. I don't have the exact config in mind but it seems to support custom uplink ports("expects IPv4 or IPv6 address specifications of DNS servers [...] optionally take a port number separated with ":"[...]")

Edit: found this: https://en.opensuse.org/Network_Management_With_Systemd