Lines Matching refs:resolver

1033     *) Feature: TCP support in resolver.
1046        response processing if the "resolver" directive was used, allowing an
1051        processing if the "resolver" directive was used, allowing an attacker
1057        "resolver" directive was used, allowing an attacker who is able to
1548     *) Bugfix: requests might hang if resolver was used and a timeout
1573     *) Bugfix: requests might hang if resolver was used and a DNS server
1813     *) Bugfix: resolver did not understand domain names with a trailing dot.
1831     *) Feature: IPv6 support in resolver.
2166        resolver was used with the poll method.
2287     *) Feature: resolver now randomly rotates addresses returned from cache.
2380        shutdown if the "resolver" directive was used.
2407     *) Feature: the "resolver" directive now supports IPv6 addresses and an
2449        "resolver" directive was used.
2557        "resolver" directive was used and there was no "error_log" directive
2731     *) Feature: the "valid" parameter of the "resolver" directive. By
2785        resolver got a big DNS response.
2804     *) Feature: support of several DNS servers in the "resolver" directive.
3259     *) Change: a logging level of resolver errors has been lowered from
3774     *) Bugfix: segmentation fault and infinite looping in resolver.
3776     *) Bugfix: in resolver.
3910     *) Bugfix: resolver cache poisoning.
3913     *) Bugfix: memory leak in resolver.
4581        "resolver" directive was used in SMTP proxy.
4721     *) Bugfix: the resolver did not understand big DNS responses.
5147     *) Feature: the "resolver" and "resolver_timeout" directives in SMTP
5166     *) Bugfix: memory leak in resolver.
5326        IP-addresses only, then a "resolver" directive is not mandatory.
5332     *) Bugfix: if resolver was used on platform that does not support
5367     *) Feature: the "resolver" and "resolver_timeout" directives.