Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UPSTREAM_DNS does not support hostnames or custom ports #145

Open
MiningMarsh opened this issue Jan 16, 2025 · 0 comments
Open

UPSTREAM_DNS does not support hostnames or custom ports #145

MiningMarsh opened this issue Jan 16, 2025 · 0 comments

Comments

@MiningMarsh
Copy link

MiningMarsh commented Jan 16, 2025

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:953

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:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant