Quoting Dimitris via Dng (dng@lists.dyne.org):
> maybe it expects you to run a local caching dns resolver :D
The best (IMO) term for what you're describing is 'recursive server',
though there's a lot of variant word usage.
I'm using connman too! :(
I just updated mine /etc/resolv to
nameserver 8.8.8.8
nameserver 8.8.4.4
and it was instantly changed to
nameserver 209.222.18.222
nameserver 209.222.18.218
Ozi
On Thu, Jul 11, 2019 at 1:31 AM Hendrik Boom wrote:
> This morning DNS wasn't working on my laptop,
On 7/10/19 6:31 PM, Hendrik Boom wrote:
> Now why would the connection manager (conman) suddenly be setting my
> nameserver to localhost?
maybe it expects you to run a local caching dns resolver :D
it might actually provide a faster experience... using
unbound/dnsmasq/others. wiki.archlinux.org
https://manpages.debian.org/stretch/connman/connman.8.en.html
Look at the -r option. Maybe that lets you disable the built-in DNS proxy. Was
that previously set somewhere?
> On 11 Jul 2019, at 01:31, Hendrik Boom wrote:
>
> This morning DNS wasn't working on my laptop, though it worked
This morning DNS wasn't working on my laptop, though it worked perfectly
well on the server it wifi-ed to.
After some pinging and checking connections, I found this on my
laptop.
The file /etc/resolv.conf:
# Generated by Connection Manager
nameserver ::1
nameserver 127.0.0.1
Now why would the
Martin Steigerwald - 08.07.19, 23:00:
> After release of Debian 10 aka Buster I just upgraded my new 64-Bit
> Devuan server from Ascii to Beowulf. The server provides mail, web and
> some other services.
>
> What can I say?
>
> It just worked.
Additionally for both of my Beowulf servers I now
