-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
When a container hosting a DNS Service is running on a user created network, container name resolution fails #23128
Comments
That is outdated. We only support the latest versions upstream. In general I don't understand how you configure the containers, please provide exact commands. |
I think this is the problem you are forwarding all traffic into your dns container so the dns queries for aardvarkd-sn will get redirected too. aardvark-dns runs on the bridge ip. As root you should see a proper failure to bind this port but given rootless runs aardvark-dns inside the rootless-netns that doe snot happen there thus the silent failure. Try using |
Oh my god how did I miss this, of course it's breaking everything it's hooked up to the host DNS port... You are a king among men, thank you for your help! This is definitely a case of user error and I appreciate you taking the time to help. |
Issue Description
Attempting to run dnsmasq or Technitium in a container while using a user created network with dns enabled causes container name resolution to fail while it the container is running.
I have not been able to find documentation about this "feature" or functionality nor a work around for having both my own dns service running while also allowing automatic resolution of the container names to their ip addresses.
Steps to reproduce the issue
Describe the results you received
The dns resolution fails and the ip address is not resolved.
Describe the results you expected
The dns resolution is successful and the ip address is resolved.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
I am running this on a Debian 12.5 headless server.
Additional information
I want to use a custom dns server to allow me to resolve a local domain instead of having to use the server's local ip address. I don't understand what or why the dns resolution is being disabled when the dnsmasq container is active. I have not been able to find documentation on having both the built in dns resolution as well as a custom dns resolution. Ideally I do not want to assign static ips to these containers and configure dnsmasq to know as this would make adding new services annoying and it seems unnecessary.
The text was updated successfully, but these errors were encountered: