Why dns resolution via aardvark-dns fails when the primary nameserver in /etc/resolv.conf is unreachable in Red Hat Enterprise Linux 9 ?

Solution Verified - Updated -

Issue

  • Why dns resolution via aardvark-dns fails when the primary nameserver in /etc/resolv.conf is unreachable in Red Hat Enterprise Linux 9 ?
    Example
# podman run -it --replace --name test1   registry.access.redhat.com/ubi9  curl  -sS login.redhat.com
curl: (6) Could not resolve host: login.redhat.com.com

Environment

  • Red Hat Enterprise Linux 9
  • rootless podman with custom network
  • aardvark-dns-1.12.2-1.el9_5.x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content