Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-52246

[RHEL EPIC] aardvark-dns needs TCP support - RHEL 9.5

XMLWordPrintable

    • aardvark-dns needs TCP support - RHEL 9.5
    • Hide

      The following needs to be verified in order for this epic to be considered complete:

      • DNS with TCP works appropriatly for ardvark-dns
      Show
      The following needs to be verified in order for this epic to be considered complete: DNS with TCP works appropriatly for ardvark-dns
    • rhel-sst-container-tools
    • 20
    • False
    • Hide

      None

      Show
      None
    • Yes
    • QE ack, Dev ack, Docs ack, PXE ack
    • Bug Fix
    • Hide
      .Netavark no longer fails resolving DNS TCP queries

      Previously, when you ran a container in a Podman network, some domain names would not resolve even though they worked on the host system or in a container not using the Podman network. With this update, Netavark supports TCP DNS queries and the problem is fixed.
      Show
      .Netavark no longer fails resolving DNS TCP queries Previously, when you ran a container in a Podman network, some domain names would not resolve even though they worked on the host system or in a container not using the Podman network. With this update, Netavark supports TCP DNS queries and the problem is fixed.
    • 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

      1. 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

       

              tsweeney@redhat.com Tom Sweeney
              tsweeney@redhat.com Tom Sweeney
              Container Runtime Eng Bot Container Runtime Eng Bot
              Container Runtime Bugs Bot Container Runtime Bugs Bot
              Gabriela Necasova Gabriela Necasova
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: