Hi,

Hendrik Boom <hendrik@???> writes:

> On Thu, Mar 20, 2025 at 08:52:12AM -0400, Dan Purgert via Dng wrote:
>> On Mar 19, 2025, Hendrik Boom wrote:
>> > [...]
>> > The problem was that connman cached DNS lookups and that somehow
>> > it has cached a dud package mirror.
>> > [...]
>> > Connman appears to hve no mechnism whatsoever to clear the cache.
>> > Years after, it is still sending me to a dud mirror whenever I upgrade.
>>
>> isn't conman(d) just a console / connection manager? Or am I looking at
>> the wrong manpages?
>
> It is a connection manager.
> But behind the scenes it rewrites resolv.conf,
> and takes over DNS lookup.
> It has its own DNS cache.
> I have searched in vain for a way to erase its cache.

I also experienced issues with connman taking over DNS lookup but *only*
with the resolution of deb.devuan.org. All other hosts I tried worked
fine. I "solved" that by creating a /etc/default/connman file with

DAEMON_OPTS=--nodnsproxy

and restarting the connman service.

Now connman defers to the DHCP server's advertised DNS servers again.
The --nodnsproxy option is documented in connman(8). The file itself is
sourced in /etc/init.d/connman.

No idea why only deb.devuan.org caused issues; deb.debian.org resolves
fine and is, TTBOMK, also using a round-robin setup.

> if I edit resolv.conf, I can bypass its DNS lookup by sending
> lookups directly to, say, 1.1.1.1.
> But this should not be necessary.
>
> -- hendrik

Hope this helps,
--
Olaf Meeuwissen