use aiodns.DNSResolver.gethostbyname() #1136
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
aiodns 1.1 has been released this weekend, it adds the support of
DNSResolver.gethostbyname()
. This PR updatesaiohttp.resolver.AsyncResolver
to use it.The main difference between
DNSResolver.query()
andgethostbyname()
is that the latter works more likegetaddrinfo()
and reads/etc/hosts
before it tries to issue a query to a DNS server. It effectively allows to use local hostnames such aslocalhost
.I don't know if it's better to require aiodns 1.1 or if the code should instead check if
gethostbyname()
is available and fallback toquery()
if not. We can also add a third Resolver class instead of modifying AsyncResolver, but it don't think that's really useful.In the first case, I will add the requirement notice in the documentation/readme/requirements, otherwise I can rewrite the PR.