You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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.
The text was updated successfully, but these errors were encountered: