flixman

@azr Excuse me for naming you explicitly here. I had posted a similar bug in the packer-plugin-ansible, but my following findings have made me think I should be reporting this...

Same here. Thank you very much, @paschun !!!!!

@hslatman Sorry for jumping in: Does this mean that if I want to generate the delegated CAs for a k8s cluster, I should generate them signed by the intermediate CA...

@hslatman Indeed! Seems to work. Thank you!

@ppisar Thank you for your answer, but this is exactly the problem I have :-/ we are producing RPMs for internal company consumption, which have the prefix set for the...

@ppisar I understand what you mean, and indeed: I have no high hopes of this being prioritised, as seems not to be much used. However, I still have the doubt:...

@Luap99 That is interesting! Let's see: Running in my container with a custom network created through ```podman network create --subnet 10.1.0.0/24 --gateway 10.1.0.1 testnet```: telnet 10.1.0.1 53, works telnet 8.8.8.8...

```dig +tcp ...``` returns the timeout as well, and aardvark-dns is running. The output of ```podman unshare --rootless-netns ss -tulpn``` is: ``` Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port...

In /etc/resolv.conf I have a bunch of name servers, and inside ```podman unshare --rootless-netns``` I have the same, but a new one gets prepended to the list ```nameserver 169.254.0.1```. When...

Indeed, it fails: ``` $ pasta --config-net --dns-forward 169.254.0.1 dig google.com @169.254.0.1 Multiple default IPv4 routes, picked first Multiple default IPv6 routes, picked first ;; communications error to 169.254.0.1#53: timed...