-
Notifications
You must be signed in to change notification settings - Fork 8
6 : Processing Flow
Chris Buijs edited this page Jan 12, 2018
·
2 revisions
PROCESS-FLOW
- Incoming Query is matched against whitelist-cache.
- If cached, processing is stopped, and DNS resolution will continue unfiltered.
- If NOT cached, query is matched against whitelists (Domain and Regex).
- If hit, result is cached and DNS resolution will continue unfiltered.
- If NOT hit, query is matched against blacklist-cache.
- If cached, query is aborted and based on config an/or RRTYPE, either REFUSED or REDIRECT is generated.
- If NOT cached, query is matched against blacklists (Domain, IP and Regex).
- If hit, result is cached and DNS resolution will abort and either REFUSED or REDIRECT is generated.
- Note: that both the QNAME and the offending DATA/ANSWER is cached in the blacklist CACHE.
- If hit, result is cached and DNS resolution will abort and either REFUSED or REDIRECT is generated.
- If NOT hit, DNS resolution proceeds normally (no filtering)
NOTE: When blocking IPv6 queries (see blockv6), this is detected/enforced during the "blacklist" section/process. Just think of it as an "always match" against blacklist when blocking IPv6 for IPv6 based queries/responses. These will always be "REFUSED" to make sure not to fill-up cache with unknown IP's.