I want to insert lancache-dns into my DNS chain, but it doesn't allow flexible enough UPSTREAM_DNS declarations.
I would like to be able to do something like this:
lancache-dns:
extra_hosts:
- some_hostname:host-gateway
environment:
- UPSTREAM_DNS=some_hostname:953This would allow me to easily forward to another DNS resolver on the same host machine (or some other container) without needing to know the gateway IP ahead of time. It would also allow me to more easily chain resolvers after lancache-dns; in my case I have an instance of stubby that bridges DNS to DNS-over-HTTPS for any device on my home network.
Right now, if you specify anything other than a plain IP, the container dies on startup:
local.lancache.dns | IP address: some_host:953 is not valid
named supports hostnames and ports natively, so I think it is just the input validation that is preventing this from working.
I want to insert lancache-dns into my DNS chain, but it doesn't allow flexible enough UPSTREAM_DNS declarations.
I would like to be able to do something like this:
This would allow me to easily forward to another DNS resolver on the same host machine (or some other container) without needing to know the gateway IP ahead of time. It would also allow me to more easily chain resolvers after lancache-dns; in my case I have an instance of stubby that bridges DNS to DNS-over-HTTPS for any device on my home network.
Right now, if you specify anything other than a plain IP, the container dies on startup:
namedsupports hostnames and ports natively, so I think it is just the input validation that is preventing this from working.