-
Notifications
You must be signed in to change notification settings - Fork 65
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
Fallback blocklist-source #313
Comments
Add |
In this case I get the error: |
By the way, I pointed to CA:
|
The ruleset-error is normal, and the previous version in the cache-dir will be used. The error is there because the list cannot be downloaded and shows the fallback actually works. The TLS error I didn't see before, and not sure if this breaks the process or not. Maybe @folbricht can shed some light on this. |
Can I use |
I tried this config:
But got the error: |
The
indicates that your OS doesn't trust the CA that was used to sign The 2nd error |
My full config is:
And with this config I get the error: |
This config looks good. The issue is that the process on your router doesn't trust public certificates either because it doesn't have those CAs in the OS, or you don't have access to them (likely the former). There a few options to deal with this:
|
Also can you check your router has DNS working at all? The error above isn't actually about cert-mismatches, but a resolution failure. Something like |
nslookup is working with commented string:
|
And I prefer option 4 to point to local certs from my USB. |
We have blocklist-remote.toml:
But if I use my web-server as source and it goes to maintenance, AND my router tries to get this BLOCKING-rules file, it will not use it and I dont want it.
Can I mix rules or use some FALLBACK option to use LOCAL source like:
Is there any way to reach this:
I will explain: if the file routedns.blocklist.domain.list is not available, routeDNS will use local domains.txt.
The text was updated successfully, but these errors were encountered: