-
Epic
-
Resolution: Done
-
Normal
-
rhel-9.5
-
aardvark-dns needs TCP support - RHEL 9.5
-
-
sst_container_tools
-
20
-
False
-
-
Yes
-
QE ack, Dev ack, Docs ack, PXE ack
-
Bug Fix
-
-
Done
Description
*From: https://issues.redhat.com/browse/RHEL-17270*
SME: pholzing@redhat.com
What were you trying to do that didn't work?
When running a container in a podman network I am not able to resolve some domain names, even though on the host system or even a container not using podman network it works OK.
Please provide the package NVR for which bug is seen:
aardvark-dns-2:1.8.0-1.el9
How reproducible:
always
Steps to reproduce
- A complete reproducer will be added to a private comment in Jira card above. From the issue https://github.com/containers/podman/issues/23239, the following will time out when tcp is not working, and will work when tcp is working.
- podman run --rm --network=pasta alpine:latest sh -c "apk add --quiet --no-cache bind-tools && cat /etc/resolv.conf && time dig +tcp google.com"
Expected results
DNS resolving works in the container
Actual results
DNS resolving doesn't work in the container
- is cloned by
-
RHEL-52247 [RHEL EPIC] aardvark-dns needs TCP support - RHEL 10.0 beta
- Closed