-
Notifications
You must be signed in to change notification settings - Fork 33
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
netavark dns resolves container fqdn on only one network when multiple networks connected #403
Comments
@flouthoc PTAL |
@ykuksenko I think OTOH you could say that bug is that short name should not get resolved by nameserver if container is not connected to the network of nameserver. |
In this scenarios the I suppose the biggest thing I would like to see is consistent behavior:
I do not see any reason for shortnames to resolve and FQDNs to fail or vise versa. If there is such a reason could you share it? I prefer having both FQDNs and shortnames to be resolvable because:
I am under the impression that netavark and aardvark-dns should combine DNS results from any network a container is connected to according to @mheon (containers/podman#14262 (comment)) |
@ykuksenko Does the requested feature works on docker cause this seems a bug a too me I think we should fix this otherway around and make short names also not resolvable if they are not part of the network. |
should this be moved to nv? |
Sorry for the delay. I do not usually use docker these days. Docker works a bit differently in this area but it does work intuitively, at least for me.
From From
Here is the list of commands I ran for setup.
From there I used the following commands to test:
Hopefully this covers everything. edit: my docker version: |
A friendly reminder that this issue had no activity for 30 days. |
Bump. Happening to me and it's very annoying! @flouthoc I can confirm this works as expected in docker, been using this networking stuff for years. In fact this issue was first reported early 2021 here: containers/podman#9492 |
@flouthoc @Luap99 @felixsanz is @ykuksenko Is this still an issue? |
I move this to aardvark-dns, looks like this is still a problem |
@ykuksenko: The label(s) In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
When a container is connected to multiple networks only one network can resolve containers by fqdn.
Steps to reproduce the issue:
Describe the results you received:
When resolving the fqdn of container1 only one name server responds correctly.
When resolving the short name of the container one both name server respond correctly
Describe the results you expected:
Both name servers should respond to both the shortname and fqdn queries.
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/main/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
Libvirt VM
The text was updated successfully, but these errors were encountered: