Correct terminology

hugepants 2021-01-23 12:31:02 +00:00
parent 9f4baefb20
commit 33e66be776

@ -245,11 +245,11 @@ config redirect
And reload Firewall: `/etc/init.d/firewall reload`
### Optional: Use `dnscrypt-proxy` for DNS rebind protection
`dnsmasq` can do [DNS rebind protection](https://openwrt.org/docs/guide-user/base-system/dhcp), but it can be useful to perform this in `dnscrypt-proxy` instead. For example, if you use a filtered DNS service like Cloudflare Security, responses from blocked domains are `0.0.0.0` which causes `dnsmasq` to fill the system log with `possible DNS-rebind attack detected` messages. Using `dnscrypt-proxy` keeps the system log clean and can still optionally log to a separate file (e.g. `ip-blocked.log`). Steps as follows:
### Optional: Use `dnscrypt-proxy` for DNS rebinding protection
`dnsmasq` can do [DNS rebinding protection](https://openwrt.org/docs/guide-user/base-system/dhcp), but it can be useful to perform this in `dnscrypt-proxy` instead. For example, if you use a filtered DNS service like Cloudflare Security, responses from blocked domains are `0.0.0.0` which causes `dnsmasq` to fill the system log with `possible DNS-rebind attack detected` messages. Using `dnscrypt-proxy` keeps the system log clean and can still optionally log to a separate file (e.g. `ip-blocked.log`). Steps as follows:
1. [Enable DNS rebind protection](https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Filters#dns-rebind-protection) in `dnscrypt-proxy` then restart `dnscrypt-proxy`
2. Disable DNS rebind protection in `dnsmasq` by setting `option rebind_protection '0'` in `/etc/config/dhcp` then restart `dnsmasq`
1. [Enable DNS rebinding protection](https://github.com/DNSCrypt/dnscrypt-proxy/wiki/Filters#dns-rebinding-protection) in `dnscrypt-proxy` then restart `dnscrypt-proxy`
2. Disable DNS rebinding protection in `dnsmasq` by setting `option rebind_protection '0'` in `/etc/config/dhcp` then restart `dnsmasq`
## Logging DNS queries with client IPs