aiodns provides a simple way for doing asynchronous DNS resolutions using pycares.
Example
import asyncio
import aiodns
loop = asyncio.get_event_loop()
resolver = aiodns.DNSResolver(loop=loop)
async def query(name, query_type):
return await resolver.query(name, query_type)
coro = query('google.com', 'A')
result = loop.run_until_complete(coro)The following query types are supported: A, AAAA, ANY, CAA, CNAME, MX, NAPTR, NS, PTR, SOA, SRV, TXT.
API
The API is pretty simple, three functions are provided in the DNSResolver class:
query(host, type): Do a DNS resolution of the given type for the given hostname. It returns an instance of asyncio.Future. The actual result of the DNS query is taken directly from pycares. As of version 1.0.0 of aiodns (and pycares, for that matter) results are always namedtuple-like objects with different attributes. Please check the documentation for the result fields.
gethostbyname(host, socket_family): Do a DNS resolution for the given hostname and the desired type of address family (i.e. socket.AF_INET). While query() always performs a request to a DNS server, gethostbyname() first looks into /etc/hosts and thus can resolve local hostnames (such as localhost). Please check the documentation for the result fields. The actual result of the call is a asyncio.Future.
gethostbyaddr(name): Make a reverse lookup for an address.
cancel(): Cancel all pending DNS queries. All futures will get DNSError exception set, with ARES_ECANCELLED errno.
Note for Windows users
This library requires the use of an asyncio.SelectorEventLoop on Windows only when using a custom build of pycares that links against a system- provided c-ares library without thread-safety support. This is because non-thread-safe builds of c-ares are incompatible with the default ProactorEventLoop on Windows.
If you’re using the official prebuilt pycares wheels on PyPI (version 4.7.0 or later), which include a thread-safe version of c-ares, this limitation does not apply and can be safely ignored.
The default event loop can be changed as follows (do this very early in your application):
asyncio.set_event_loop_policy(asyncio.WindowsSelectorEventLoopPolicy())This may have other implications for the rest of your codebase, so make sure to test thoroughly.
Running the test suite
To run the test suite: python tests.py
License
aiodns uses the MIT license, check LICENSE file.
Contributing
If you’d like to contribute, fork the project, make a patch and send a pull request. Have a look at the surrounding code and please, make yours look alike :-)
1 maintainer
Metadata
1 maintainer
Release files for aiodns 3.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| aiodns-3.3.0.tar.gz | 8.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| aiodns-3.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.7 kB
Release files / aiodns-3.3.0.tar.gz
| Download URL | aiodns-3.3.0.tar.gz |
|---|---|
| Size | 8.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fdf7a7d51dcab0ad7cc22bf9cf54690d9c31b06414ac41c6cdbbecf50dd75ef1
|
|
BLAKE2b-256 checksum How to use checksums |
f6302c10dc401091beffef6f516da38f7e6391d2a77afe5e092956855e1d07a7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 2, 2025.
Transparency logRelease files / aiodns-3.3.0-py3-none-any.whl
| Download URL | aiodns-3.3.0-py3-none-any.whl |
|---|---|
| Size | 6.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
10773b905296afd92d41ef79b9ed0c97957d9af17262ffa67f405dc07f1600a4
|
|
BLAKE2b-256 checksum How to use checksums |
565577e04056918323e913cbd706063c0cc045717741432eb5cce432a808e05d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 2, 2025.
Transparency log
