On Tue, Sep 07, 2021 at 04:41:49PM -0700, Don Armstrong wrote: > On Mon, 06 Sep 2021, Mattia Rizzolo wrote: > > It must be noted that no actual network operation happen, so this > > doesn't fall into the "no network activity" bucket. > > > > This is the bug that was filed against dnspython: > > https://bugs.debian.org/989171 > > > > Do anybody on the list have any opinion on where is the bug, on > > dnspython, or on the build environment? > > Do you know why dnspython doesn't just fall back to socket.getaddrinfo > if it can't parse /etc/resolv.conf [or maybe why python applications > using dnspython don't fall back to that if dnspython fails?] > > That seems like the right default unless you really, really need to talk > to a full-fledged DNS server directly.
https://github.com/rthalley/dnspython dnspython provides both high and low level access to DNS. The high level classes perform queries for data of a given name, type, and class, and return an answer set. The low level classes allow direct manipulation of DNS zones, messages, names, and records. ... dnspython is a utility to work with DNS, /etc/hosts is thus not used. For simple forward DNS lookups, it's better to use socket.getaddrinfo() or socket.gethostbyname(). dnspython originated at Nominum where it was developed to facilitate the testing of DNS software. cu Adrian
