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

Parse error while parsing upstreams configuration from a text file #409

Open
andreydegt opened this issue Aug 3, 2024 · 2 comments
Open

Comments

@andreydegt
Copy link

OpenWRT 23.05.4, dnsproxy v0.67.0.
Part of config for service:

config dnsproxy 'servers'
list bootstrap 'tls://8.8.8.8'
list fallback '/etc/dnsproxy/fallback_list'
list upstream '/etc/dnsproxy/dnslist'

I get an error with this:
Sat Aug 3 15:20:45 2024 daemon.err dnsproxy[12495]: 2024/08/03 12:20:45 [fatal] error while parsing upstreams configuration: parsing error at index 0: cannot prepare the upstream: invalid address /etc/dnsproxy/dnslist: bad hostname "/etc/dnsproxy/dnslist": bad top-level domain name label "/etc/dnsproxy/dnslist": bad top-level domain name label rune '/'

But when I run dnsproxy from console it works. For example:

dnsproxy -l 127.0.2.1 -p 5354 -u /etc/dnsproxy/dnslist

In previous versions, reading from a file worked fine.

@ainar-g
Copy link
Contributor

ainar-g commented Aug 5, 2024

I cannot reproduce this. Can you reproduce this with dnsproxy itself as opposed to the OpenWrt package? Because it might be a package issue.

@andreydegt
Copy link
Author

I don't see a way to do this yet. The strange thing here is that after receiving the upstream as a text file via the console, DNSproxy works fine.
But after receiving the same upstream, it gives an error when starting the service.
After all, the log says what exactly DNSproxy doesn't like.
In the case when a real DNS is specified as an upstream in the config, this works fine. If it's a text file, this leads to an error.

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

No branches or pull requests

2 participants