Paul Holzinger

We use `dns.podman` by default as search domain. So `containerA.dns.podman` should resolve fine. It is not per network though. Adding the network name as zones tracked and described in https://github.com/containers/aardvark-dns/issues/403...

That name pre-dates me and was coming form our cni dnsname implementation. Changing that now would break users depending on it. Also I think we explicitly block dns.podman from being...

> No. I am looking for a way to configure unbound on host machine to forward container names and container network IP ranges to podman managed dns service. For example...

I would assume so, nothing has changed and my reproducer still fails with the same error message In general restoring the network namespace for a userns is currently broken anyways...

putting this test in dbus/dbus_test.go ``` func TestGithubIssue(t *testing.T) { ctx := context.Background() dbusConn, err := NewUserConnectionContext(ctx) if err != nil { t.Fatalf("NewUserConnectionContext") } defer dbusConn.Close() res, err := dbusConn.GetUnitPropertiesContext(ctx,...