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
There needs to be a way to reload filters without restarting DNSCrypt-Proxy.
In all fairness, DNSCrypt-Proxy does "seem" to restart quite fast, by human standards, but still not as fast as to have some services on my server fail due to lack of DNS resolver.
In my use case, those services are critical.
From the top of my head, a really stupid way of circumvent it, would be have 2 instances of DNSCrypt running ("backup" and "production"), and have iptables redirect traffic from "production" to "backup", restart DNSCrypt "production", and change iptables to remove redirection. Even then, I'm not sure it would work.
Surely there is a better way of handling reload of blacklists in DNSCrypt-Proxy without losing DNS resolution.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
There needs to be a way to reload filters without restarting DNSCrypt-Proxy.
In all fairness, DNSCrypt-Proxy does "seem" to restart quite fast, by human standards, but still not as fast as to have some services on my server fail due to lack of DNS resolver.
In my use case, those services are critical.
From the top of my head, a really stupid way of circumvent it, would be have 2 instances of DNSCrypt running ("backup" and "production"), and have iptables redirect traffic from "production" to "backup", restart DNSCrypt "production", and change iptables to remove redirection. Even then, I'm not sure it would work.
Surely there is a better way of handling reload of blacklists in DNSCrypt-Proxy without losing DNS resolution.
Beta Was this translation helpful? Give feedback.
All reactions