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
allow to set HTTP PROXY for HTTP/S access while still using non-proxied DNS over UDP forwarders #892
Comments
Thanks for the post.
You can still do that using conditional forwarder zones. Just configure the proxy in Settings > Proxy & Forwarders section without any forwarders and create a conditional forwarder zone for
Please share the error details here. You should also see the error log in the Logs section on the panel. |
The error show is a red alert box with following text
|
The error means that you configured HTTP proxy but you also had forwarders configured to use either UDP or QUIC transport protocol which is not support by the HTTP proxy protocol. So, you just need to either configure a SOCKS5 proxy or change your forwarder protocol. Also, since there was the error when you tried to save settings, the settings were not saved to disk. |
@ShreyasZare I did understand the error message. However here is my problem in my particular setup:
I do understand that UDP cannot use HTTP proxy. But why not just show an information that since I selected UDP and an unsupported PROXY it's just not going to use the proxy for UDP (but very much so for HTTP). |
The solution for this requirement is to use conditional forwarder zones instead of the forwarders in the settings.
Its not like that. Due to the validation error, the settings were not fully updated and saved. In such a case, the DNS client will internally switch to use TCP transport instead of UDP transport to make it work over the HTTP proxy. The error message is just so that the config is correct. |
In my setup I need to use an HTTP PROXY to access the update check and to download blocklists via HTTP/S, but I still want to use plain simple DNS over UDP forwarders (in my case to allow a NG-FW appliance to scan the requests).
Currently the WebUI displays an error and the configuration doesn't seem to survive a daemon restart.
The text was updated successfully, but these errors were encountered: