Your message dated Sat, 01 Jul 2023 16:54:17 -0400
with message-id <2486509.HnpLNgO9na@localhost>
and subject line Re: python-dns: no useable dns server found when using caching 
dns e.g. only one entry in resolv.conf
has caused the Debian Bug report #877785,
regarding python-dns: no useable dns server found when using caching dns e.g. 
only one entry in resolv.conf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
877785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877785
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-dnspython
Version: 1.15.0-1
Severity: normal
File: python-dns

Dear Maintainer,


I'm using local dns-cache to speed up lookups, my /etc/resolv.conf basically 
looks like
====
nameserver 127.0.0.1
====

Trying to do SPF lookups using postfix-policyd-spf led to temperrors, using 
debug mode showed
the error message "no useable dns servers found".

It goes back to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378991
when a patch has beend applied to get at least one nameserver when the first 
entry is for
search domain or something else than a valid nameserver entry.

This is an unexpected behaviour since the system does in fact have one, the 
local caching
DNS uses a seperate config-file for its nameservers.

The detection needs to be rwritten to make sure a valid nameserver has been 
found instead of
counting the lines.

To fix the issue ( if one knows what he's doing ) I had to comment out linde 63 
and 64 in
/usr/lib/python3/dist-packages/DNS/Base.py
====
        if len(fields) < 2:
            continue
====

-- System Information:
Debian Release: 9.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (499, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.10.17-3-pve (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages python-dnspython depends on:
ii  python  2.7.13-2

python-dnspython recommends no packages.

python-dnspython suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
On Thu, 05 Oct 2017 18:14:59 +0200 Christoph Zysik <[email protected]> wrote:
> Package: python-dnspython
> Version: 1.15.0-1
> Severity: normal
> File: python-dns
> 
> Dear Maintainer,
> 
> 
> I'm using local dns-cache to speed up lookups, my /etc/resolv.conf basically 
looks like
> ====
> nameserver 127.0.0.1
> ====
> 
> Trying to do SPF lookups using postfix-policyd-spf led to temperrors, using 
debug mode showed
> the error message "no useable dns servers found".
> 
> It goes back to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378991
> when a patch has beend applied to get at least one nameserver when the first 
entry is for
> search domain or something else than a valid nameserver entry.
> 
> This is an unexpected behaviour since the system does in fact have one, the 
local caching
> DNS uses a seperate config-file for its nameservers.
> 
> The detection needs to be rwritten to make sure a valid nameserver has been 
found instead of
> counting the lines.
> 
> To fix the issue ( if one knows what he's doing ) I had to comment out linde 
63 and 64 in
> /usr/lib/python3/dist-packages/DNS/Base.py
> ====
>         if len(fields) < 2:
>             continue
> ====

I'm working on py3dns for the first time since this was assigned to the correct 
package.  The analysis in the bug is in error.  The variable fields is the 
number of fields on a line, not the number of lines.  I don't know what caused 
this problem at the time, but I've tested with a one line /etc/resolve.conf 
and it works fine as of now, so closing the bug.

Scott K

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---

Reply via email to