mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
Remove 'dns_resolver' option, replace w/ ZEEK_DNS_RESOLVER env. var.
The later simply doesn't work well in conjunction with hostname literals. i.e. "google.com" (without quotes) needs to be resolved to a set of addresses at parse-time, so if a user wishes to use a custom resolver, we need that to be configured independently from the order in which scripts get parsed. Configuring 'dns_resolver' via scripting "redef" is clearly dependent on parse order. Note 'dns_resolver' hasn't been in any release version yet, so I'm removing it outright, no deprecation. The ZEEK_DNS_RESOLVER environment variable now serves the original purpose.
This commit is contained in:
parent
49908ac865
commit
f7c1cde7c7
5 changed files with 29 additions and 36 deletions
|
@ -3743,12 +3743,6 @@ global dns_skip_all_addl = T &redef;
|
|||
## traffic and do not process it. Set to 0 to turn off this functionality.
|
||||
global dns_max_queries = 25 &redef;
|
||||
|
||||
## The address of the DNS resolver to use. If not changed from the
|
||||
## unspecified address, ``[::]``, the first nameserver from /etc/resolv.conf
|
||||
## gets used (IPv6 is currently only supported if set via this option, not
|
||||
## when parsed from the file).
|
||||
const dns_resolver = [::] &redef;
|
||||
|
||||
## HTTP session statistics.
|
||||
##
|
||||
## .. zeek:see:: http_stats
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue