Use of deprecated dnspython method

[blink1073]

From the dnspython 2.0 release notes, "dns.resolver.resolve() has been added, allowing control of whether search lists are used. dns.resolver.query() is retained for backwards compatibility, but deprecated".

Example traceback (with warnings turned to errors):

.../site-packages/eventlet/support/greendns.py:549: in getaddrinfo
    qname, addrs = _getaddrinfo_lookup(host, family, flags)
.../site-packages/eventlet/support/greendns.py:511: in _getaddrinfo_lookup
    answer = resolve(host, qfamily, False, use_network=use_network)
.../site-packages/eventlet/support/greendns.py:456: in resolve
    return _proxy.query(name, rdtype, raise_on_no_answer=raises,
.../site-packages/eventlet/support/greendns.py:412: in query
    return end()
.../site-packages/eventlet/support/greendns.py:391: in end
    raise result[1]
.../site-packages/eventlet/support/greendns.py:372: in step
    a = fun(*args, **kwargs)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
    def query(
        self,
        qname: Union[dns.name.Name, str],
        rdtype: Union[dns.rdatatype.RdataType, str] = dns.rdatatype.A,
        rdclass: Union[dns.rdataclass.RdataClass, str] = dns.rdataclass.IN,
        tcp: bool = False,
        source: Optional[str] = None,
        raise_on_no_answer: bool = True,
        source_port: int = 0,
        lifetime: Optional[float] = None,
    ) -> Answer:  # pragma: no cover
        """Query nameservers to find the answer to the question.

        This method calls resolve() with ``search=True``, and is
        provided for backwards compatibility with prior versions of
        dnspython.  See the documentation for the resolve() method for
        further details.
        """
>       warnings.warn(
            "please use dns.resolver.Resolver.resolve() instead",
            DeprecationWarning,
            stacklevel=2,
        )
E       DeprecationWarning: please use dns.resolver.Resolver.resolve() instead
.../site-packages/dns/resolver.py:1359: DeprecationWarning

[4383]

Hello,

Thanks for reporting this issue. Do you want to create a pull request?

[4383]

I just proposed a patch to move to the usages to resolve. Feel free to comment #840