3 ms·
> If there's a clean way to resolve this, so that the VM itself can just send `.internal` queries to us, and everything else to `1.1.1.1` or `8.8.8.8` or whatev
by BeefWellington 6y ago
> If there's a clean way to resolve this, so that the VM itself can just send `.internal` queries to us, and everything else to `1.1.1.1` or `8.8.8.8` or whatever the customer's container had, I would _love_ to hear it. I've come pretty close to breaking out preload in anger over this problem.
If you're at that point, rather than preload, why not simply add the code to glibc and contribute it back? Has there been some resistance from the maintainers already?
It would seem like it should be doable to add it on in a safe way, e.g. something that would work for both:
`nameserver 192.168.0.1`
and
```
nameserver 192.168.0.1
nameserver 10.10.10.1 .internal .private .etc
```
Even if there's hesitance in accepting a change to the `nameserver` options, you easily make this an option, e.g.:
`options tld-nameserver:.internal:<addr>`
- lmz 6y agoThis just adds more complexity to a universally used user space library. And also breaks when some programs don't use the same resolver. Just implement your own dns server that does it for you (or reuse dnsmasq).