The Sisyphean Task of DNS Client Config on Linux

Re:The Sisyphean Task of DNS Client Config on Linux by tptacek on Thursday April 15, 2021 @04:07PM (#26825513)

I'm not sure how reasonable it is for us to run systemd-resolved (or systemd itself) on our VMs. We're trying to provide a clean environment for any random container to run on; we provide our own init, and that's almost the whole of it.

What, I think, you really care about here is glibc's behavior. But then, you can't depend on any one libc, either.

[ Parent | on HN ]

Re:The Sisyphean Task of DNS Client Config on Linux by recuter on Thursday April 15, 2021 @04:24PM (#26825669)

The cliffs of cloud native software defined networking insanity await you:

https://github.com/containernetworking/cni

https://github.com/firecracker-microvm/firecracker-go-sdk

  Firecracker, by design, only supports Linux tap devices. The SDK provides facilities to:

  Attach a pre-created tap device, optionally with static IP configuration, to the VM. This is referred to as a "static network interface".
  Create a tap device via CNI plugins, which will then be attached to the VM automatically by the SDK. This is referred to as a "CNI-configured network interface"

[ Parent | on HN ]

Re:The Sisyphean Task of DNS Client Config on Linux by YarickR2 on Thursday April 15, 2021 @04:32PM (#26825765)

It's unreasonable to bring the whole cow to just get a gallon of milk . Use standalone resolver.

[ Parent | on HN ]