Anyone of you #Python #developers works with #dnspython? The documentation says there is a timeout field implemented. I am working with v2.8.0, and my interpreter complains that there is no argument called timeout. Same holds for the lifetime argument.
Solved it, by adding it to the Resolver.resolve() function. But I still expected it to be in the actual code.
Is this a bug, and the docs differ from the code?
Does anyone know why #DNSPython hangs, when run under #GithubActions, while being imported?
Thanks
I decided to add #DoQ support to my check_soa script (because it's easy to add as #dnspython supports it pretty much out of the box) so I'm looking for #DNS zones using authoritative nameservers accessible with DoQ. Does anyone knows any?
I know a few recursive servers using #QUIC but I haven't found authoritative servers yet :/
(I'd love to have some myself (my NS can be already be queried using #DoT) but I use #NSD (which has no QUIC support yet) and Debian so...)
Oops, the recently released #dnspython 2.6.0 added support for the EDNS NSID option, thus breaking my check_soa scripts. Need to add temporary dnspython version check
(And I should move these scripts in a proper repo)
Grumph, une erreur dans la doc de #dnspython :
Le 'target' ici n'est pas un dns.name.Name, mais un bête tas d'octets (bytes donc)
https://dnspython.readthedocs.io/en/stable/rdata-subclasses.html#dns.rdtypes.ANY.URI.URI
Another curious #musl libc issue: `getaddrinfo()` fills `.ai_canonname` even if `AI_CANONNAME` is not passed in `flags`. Apparently not a big deal, except that it breaks the tests of #DNSPython when present unexpectedly. Technically, it may also not comply to #POSIX, though I'm not sure.
https://www.openwall.com/lists/musl/2024/01/27/5
https://github.com/rthalley/dnspython/issues/1035
https://bugs.gentoo.org/923004
Kolejny ciekawy problem z #musl libc: `getaddrinfo()` wypełnia pole `.ai_canonname`, nawet jeśli `flags` nie zawiera `AI_CANONNAME`. Niby to nic wielkiego, ale wystarcza, żeby popsuć testy #DNSPython. Technicznie rzecz biorąc, może to być też niezgodne z #POSIX, ale nie mam pewności.
https://www.openwall.com/lists/musl/2024/01/27/5
https://github.com/rthalley/dnspython/issues/1035
https://bugs.gentoo.org/923004
#dnspython 2.5 released
Among the changes, still no options to generate #NSEC3 signatures when using the zone signing function, but it seems it's coming : "[t]he NSEC3 class now has a next_name() method for retrieving the next name as a dns.name.Name"
https://dnspython.readthedocs.io/en/stable/whatsnew.html#id1
Why is #dnspython packaged like that? Why can't I just import dns?
Now I have to import dns.a.b.c and then use dns.a.b.c.c
WTF.
Alone naming your package like that is... Why not dnspython? Then we can use install==import.
Really reminds me of some Google gcp packages.
With #dnspython 2.4.0+, @DNSresolver can be configured to use a DoH resolver without changes in the current code.
DoQ and DoT requires minimal changes
🤔
Max Resing
iam-py-test
John Shaft
Jesus Michał "Le Sigh" 🏔 (he)
Jezus Michał "Le Wzdych" (on)
Fink 