Open shekharHPE opened 5 years ago
Hi, I don't know is it still relevant. I tried two different ways:
/etc/netns
directory before creating the namespace OR forcing sudo resolvconf -u
in netns after;The first one looks more natural, but I agree - both are workarounds
/etc/resolv.conf
is an ordinary file, read by many DNS client libraries./etc/resolv.conf
is subject to mount namespaces, but not network namespaces./etc/resolv.conf
from its currently active mount namespace, and if you don't change that to the one used by your boxed processes using separate different network and mount namespaces, your process uses the wrong /etc/resolv.conf
.
We have a resolv.conf file for every namespaces. When switching from one namespace (say VRF_1) to another (say VRF_2), it seems that the resolv.conf file attached to VRF_1 is used to resolve the DNS instead of VRF_2. Is there any way as of today to ensure use of a different resolv.conf while switching the namespace.