Right, I've also heard about the special interface solution before.
Not sure how exactly it works though.
Can't claim to be an expert on the implementation details either, sorry.
I see. In that case, maybe we could have local resolver listening
on multiple network interfaces. But how would container know which
interface it should connect to? As in, is 169.254.169.254 consistent
across various container solutions(Docker/Rocket/LXC etc.)?
Docker already supports a --dns option on the commandline to pass details for /etc/resolv.conf. For the various container solutions, I'd expect providing a standard consumable location for the resolver would be a good start. A container specific implementation looks like a slippery slope.
-Matt M