From grlug at grlug.org  Fri Sep 11 16:53:32 2020
From: grlug at grlug.org (Grand Rapids Linux Users Group)
Date: Fri, 11 Sep 2020 15:53:32 -0500 (CDT)
Subject: [GRLUG] St. Louis LUG Meeting next Thursday
Message-ID: <mailman.46889.1599857623.100365.grlug@grlug.org>

TOPIC:   SuSE  CEPH fs. Uyuni. SUMA. SuSE Manager.

September 17, '20 for the montly St. Louis Linux Users Group meeting.
Michael Carrington of SuSE, will be bringing the group up to speed on the
latest in the CEPH filesystem as well as a demonstration - a follow up to
the talk Michael gave us in January 2020.

And Patrick Schwartz of SuSE, will be speaking to the open source project
Uyuni, for which SUSE offers management and support on under SUMA or SUSE
Manager.

From grlug at grlug.org  Fri Sep 18 21:59:17 2020
From: grlug at grlug.org (Grand Rapids Linux Users Group)
Date: Fri, 18 Sep 2020 20:59:17 -0500 (CDT)
Subject: [GRLUG] systemd DNS
Message-ID: <mailman.46890.1600480766.100365.grlug@grlug.org>

Have a VPS that came configured to use systemd DNS, .. and every now and
then resolution fails (there are Nagios checks checking for the various
websites on that server).

Anyone ever seen such a transient failures?

        Thanks!

From grlug at grlug.org  Sun Sep 20 19:18:09 2020
From: grlug at grlug.org (Grand Rapids Linux Users Group)
Date: Sun, 20 Sep 2020 16:18:09 -0700
Subject: [GRLUG] systemd DNS
In-Reply-To: <mailman.46890.1600480766.100365.grlug@grlug.org>
References: <mailman.46890.1600480766.100365.grlug@grlug.org>
Message-ID: <mailman.46891.1600643894.100365.grlug@grlug.org>

I’ve been underwhelmed by systemd DNS for a few months, and am working through it’s implementation on both ubuntu and centos to determine why / where it gets its hooks, but haven’t found a real fix for it, yet.  There are ways to inject nameservers / search domain.tld / etc. using NetworkManager, network/ing.service, internal dhcp or dhclient, but none are consistently implemented and you end up with hosts that fail to resolve internal and external fqdns until you trounce /etc/resolv.conf with a sane version of nameservers for your network.

Currently netplan appears to be the most reasonable management option, but I’m still working through it’s implementation and deployment.  One of the challenges, I’m running into is that I’m migrating my VirtualBox VMs to libvirt / KVM, which adds the additional complication of configuring bonding, but have mostly worked through those details and have a good netplan configuration for the kvm nodes, just need to finalize how to reapply the netplan on running hosts without disrupting networking on the various guests when network changes happen.

If anyone else is also working on ways to replace systemd’s brain-dead DNS implementation, I’d be interested in seeing what you’re experiencing.  Seems a good problem to gather collaborators for, especially those using different distros, such as centos, ubuntu, suse, etc.

-Van

> On Sep 18, 2020, at 18:59, Grand Rapids Linux Users Group <grlug at grlug.org> wrote:
> 
> Have a VPS that came configured to use systemd DNS, .. and every now and
> then resolution fails (there are Nagios checks checking for the various
> websites on that server).
> 
> Anyone ever seen such a transient failures?
> 
>        Thanks!
> -- 
> grlug mailing list
> grlug at grlug.org
> https://shinobu.grlug.org/mailman/listinfo/grlug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://shinobu.grlug.org/pipermail/grlug/attachments/20200920/778f4b02/attachment.html>

From grlug at grlug.org  Mon Sep 21 13:19:01 2020
From: grlug at grlug.org (Grand Rapids Linux Users Group)
Date: Mon, 21 Sep 2020 13:19:01 -0400
Subject: [GRLUG] systemd DNS
In-Reply-To: <mailman.46891.1600643894.100365.grlug@grlug.org>
References: <mailman.46890.1600480766.100365.grlug@grlug.org>
 <mailman.46891.1600643894.100365.grlug@grlug.org>
Message-ID: <mailman.46892.1600708746.100365.grlug@grlug.org>

I'm more used to using BIND DNS as a recursive resolver and/or 
machine-local caching resolver.  It may be older, but if it ain't broke, 
don't fix it.  So, if it's available to you (depending on how much 
control you have of the environment you run in), you might want to give 
it a try.  It's easy to set up and boringly reliable.

Warm Regards,
Kyle Maas



On 9/20/20 7:18 PM, Grand Rapids Linux Users Group wrote:
> I’ve been underwhelmed by systemd DNS for a few months, and am working 
> through it’s implementation on both ubuntu and centos to determine why 
> / where it gets its hooks, but haven’t found a real fix for it, yet. 
>  There are ways to inject nameservers / search domain.tld / etc. using 
> NetworkManager, network/ing.service, internal dhcp or dhclient, but 
> none are consistently implemented and you end up with hosts that fail 
> to resolve internal and external fqdns until you trounce 
> /etc/resolv.conf with a sane version of nameservers for your network.
>
> Currently netplan appears to be the most reasonable management option, 
> but I’m still working through it’s implementation and deployment.  One 
> of the challenges, I’m running into is that I’m migrating my 
> VirtualBox VMs to libvirt / KVM, which adds the additional 
> complication of configuring bonding, but have mostly worked through 
> those details and have a good netplan configuration for the kvm nodes, 
> just need to finalize how to reapply the netplan on running hosts 
> without disrupting networking on the various guests when network 
> changes happen.
>
> If anyone else is also working on ways to replace systemd’s brain-dead 
> DNS implementation, I’d be interested in seeing what you’re 
> experiencing.  Seems a good problem to gather collaborators for, 
> especially those using different distros, such as centos, ubuntu, 
> suse, etc.
>
> -Van
>
>> On Sep 18, 2020, at 18:59, Grand Rapids Linux Users Group 
>> <grlug at grlug.org <mailto:grlug at grlug.org>> wrote:
>>
>> Have a VPS that came configured to use systemd DNS, .. and every now and
>> then resolution fails (there are Nagios checks checking for the various
>> websites on that server).
>>
>> Anyone ever seen such a transient failures?
>>
>>        Thanks!
>> -- 
>> grlug mailing list
>> grlug at grlug.org <mailto:grlug at grlug.org>
>> https://shinobu.grlug.org/mailman/listinfo/grlug
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://shinobu.grlug.org/pipermail/grlug/attachments/20200921/f8c2360e/attachment.html>

From grlug at grlug.org  Mon Sep 21 13:22:44 2020
From: grlug at grlug.org (Grand Rapids Linux Users Group)
Date: Mon, 21 Sep 2020 13:22:44 -0400
Subject: [GRLUG] systemd DNS
In-Reply-To: <mailman.46892.1600708746.100365.grlug@grlug.org>
References: <mailman.46890.1600480766.100365.grlug@grlug.org>
 <mailman.46891.1600643894.100365.grlug@grlug.org>
 <mailman.46892.1600708746.100365.grlug@grlug.org>
Message-ID: <mailman.46893.1600708978.100365.grlug@grlug.org>

We've had a ton of issues with systemd DNS resolver doing silly things like
crashing and causing huge issues since all resolution fails. (notably, I
haven't tried it in probably a year, so maybe newer versions are better),
but it seems to me, adding something into the DNS resolver path is just
adding another point of failure.

If you do really need DNS caching, check out unbound.  It's super
fast/lightweight (compared to BIND), if you're just doing caching..  For
all my internal stuff, I disable systemd's resolver, and use unbound.

On Mon, Sep 21, 2020 at 1:19 PM Grand Rapids Linux Users Group <
grlug at grlug.org> wrote:

> I'm more used to using BIND DNS as a recursive resolver and/or
> machine-local caching resolver.  It may be older, but if it ain't broke,
> don't fix it.  So, if it's available to you (depending on how much control
> you have of the environment you run in), you might want to give it a try.
> It's easy to set up and boringly reliable.
>
> Warm Regards,
> Kyle Maas
>
>
>
> On 9/20/20 7:18 PM, Grand Rapids Linux Users Group wrote:
>
> I’ve been underwhelmed by systemd DNS for a few months, and am working
> through it’s implementation on both ubuntu and centos to determine why /
> where it gets its hooks, but haven’t found a real fix for it, yet.  There
> are ways to inject nameservers / search domain.tld / etc. using
> NetworkManager, network/ing.service, internal dhcp or dhclient, but none
> are consistently implemented and you end up with hosts that fail to resolve
> internal and external fqdns until you trounce /etc/resolv.conf with a sane
> version of nameservers for your network.
>
> Currently netplan appears to be the most reasonable management option, but
> I’m still working through it’s implementation and deployment.  One of the
> challenges, I’m running into is that I’m migrating my VirtualBox VMs to
> libvirt / KVM, which adds the additional complication of configuring
> bonding, but have mostly worked through those details and have a good
> netplan configuration for the kvm nodes, just need to finalize how to
> reapply the netplan on running hosts without disrupting networking on the
> various guests when network changes happen.
>
> If anyone else is also working on ways to replace systemd’s brain-dead DNS
> implementation, I’d be interested in seeing what you’re experiencing.
> Seems a good problem to gather collaborators for, especially those using
> different distros, such as centos, ubuntu, suse, etc.
>
> -Van
>
> On Sep 18, 2020, at 18:59, Grand Rapids Linux Users Group <grlug at grlug.org>
> wrote:
>
> Have a VPS that came configured to use systemd DNS, .. and every now and
> then resolution fails (there are Nagios checks checking for the various
> websites on that server).
>
> Anyone ever seen such a transient failures?
>
>        Thanks!
> --
> grlug mailing list
> grlug at grlug.org
> https://shinobu.grlug.org/mailman/listinfo/grlug
>
>
>
>
> --
> grlug mailing list
> grlug at grlug.org
> https://shinobu.grlug.org/mailman/listinfo/grlug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://shinobu.grlug.org/pipermail/grlug/attachments/20200921/4ee2fb2b/attachment.html>

From grlug at grlug.org  Mon Sep 21 14:35:13 2020
From: grlug at grlug.org (Grand Rapids Linux Users Group)
Date: Mon, 21 Sep 2020 14:35:13 -0400
Subject: [GRLUG] systemd DNS
In-Reply-To: <mailman.46893.1600708978.100365.grlug@grlug.org>
References: <mailman.46890.1600480766.100365.grlug@grlug.org>
 <mailman.46891.1600643894.100365.grlug@grlug.org>
 <mailman.46892.1600708746.100365.grlug@grlug.org>
 <mailman.46893.1600708978.100365.grlug@grlug.org>
Message-ID: <mailman.46894.1600713290.100365.grlug@grlug.org>

+1 for unbound

it has a great internal record factory, that’s very versatile, with lots of failsafes, and fallbacks, and it plays nicely with redis (can consume a previously dumped cache).



-j





> On Sep 21, 2020, at 1:22 PM, Grand Rapids Linux Users Group <grlug at grlug.org> wrote:
> 
> We've had a ton of issues with systemd DNS resolver doing silly things like crashing and causing huge issues since all resolution fails. (notably, I haven't tried it in probably a year, so maybe newer versions are better), but it seems to me, adding something into the DNS resolver path is just adding another point of failure.
> 
> If you do really need DNS caching, check out unbound.  It's super fast/lightweight (compared to BIND), if you're just doing caching..  For all my internal stuff, I disable systemd's resolver, and use unbound.
> 
> On Mon, Sep 21, 2020 at 1:19 PM Grand Rapids Linux Users Group <grlug at grlug.org <mailto:grlug at grlug.org>> wrote:
> I'm more used to using BIND DNS as a recursive resolver and/or machine-local caching resolver.  It may be older, but if it ain't broke, don't fix it.  So, if it's available to you (depending on how much control you have of the environment you run in), you might want to give it a try.  It's easy to set up and boringly reliable.
> 
> Warm Regards,
> Kyle Maas
> 
> 
> 
> On 9/20/20 7:18 PM, Grand Rapids Linux Users Group wrote:
>> I’ve been underwhelmed by systemd DNS for a few months, and am working through it’s implementation on both ubuntu and centos to determine why / where it gets its hooks, but haven’t found a real fix for it, yet.  There are ways to inject nameservers / search domain.tld / etc. using NetworkManager, network/ing.service, internal dhcp or dhclient, but none are consistently implemented and you end up with hosts that fail to resolve internal and external fqdns until you trounce /etc/resolv.conf with a sane version of nameservers for your network.
>> 
>> Currently netplan appears to be the most reasonable management option, but I’m still working through it’s implementation and deployment.  One of the challenges, I’m running into is that I’m migrating my VirtualBox VMs to libvirt / KVM, which adds the additional complication of configuring bonding, but have mostly worked through those details and have a good netplan configuration for the kvm nodes, just need to finalize how to reapply the netplan on running hosts without disrupting networking on the various guests when network changes happen.
>> 
>> If anyone else is also working on ways to replace systemd’s brain-dead DNS implementation, I’d be interested in seeing what you’re experiencing.  Seems a good problem to gather collaborators for, especially those using different distros, such as centos, ubuntu, suse, etc.
>> 
>> -Van
>> 
>>> On Sep 18, 2020, at 18:59, Grand Rapids Linux Users Group <grlug at grlug.org <mailto:grlug at grlug.org>> wrote:
>>> 
>>> Have a VPS that came configured to use systemd DNS, .. and every now and
>>> then resolution fails (there are Nagios checks checking for the various
>>> websites on that server).
>>> 
>>> Anyone ever seen such a transient failures?
>>> 
>>>        Thanks!
>>> -- 
>>> grlug mailing list
>>> grlug at grlug.org <mailto:grlug at grlug.org>
>>> https://shinobu.grlug.org/mailman/listinfo/grlug <https://shinobu.grlug.org/mailman/listinfo/grlug>
>> 
>> 
> 
> -- 
> grlug mailing list
> grlug at grlug.org <mailto:grlug at grlug.org>
> https://shinobu.grlug.org/mailman/listinfo/grlug <https://shinobu.grlug.org/mailman/listinfo/grlug>
> -- 
> grlug mailing list
> grlug at grlug.org
> https://shinobu.grlug.org/mailman/listinfo/grlug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://shinobu.grlug.org/pipermail/grlug/attachments/20200921/7d99baba/attachment-0001.html>

From grlug at grlug.org  Mon Sep 21 15:23:06 2020
From: grlug at grlug.org (Grand Rapids Linux Users Group)
Date: Mon, 21 Sep 2020 15:23:06 -0400
Subject: [GRLUG] systemd DNS
In-Reply-To: <mailman.46893.1600708978.100365.grlug@grlug.org>
References: <mailman.46890.1600480766.100365.grlug@grlug.org>
 <mailman.46891.1600643894.100365.grlug@grlug.org>
 <mailman.46892.1600708746.100365.grlug@grlug.org>
 <mailman.46893.1600708978.100365.grlug@grlug.org>
Message-ID: <mailman.46897.1600716189.100365.grlug@grlug.org>

Sorry, apparently I wasn't clear.  I meant BIND DNS as an alternative to 
systemd, not as an adjunct.

Can't speak for unbound - have never tried it.

Warm Regards,
Kyle Maas



On 9/21/20 1:22 PM, Grand Rapids Linux Users Group wrote:
> We've had a ton of issues with systemd DNS resolver doing silly things 
> like crashing and causing huge issues since all resolution fails. 
> (notably, I haven't tried it in probably a year, so maybe newer 
> versions are better), but it seems to me, adding something into the 
> DNS resolver path is just adding another point of failure.
>
> If you do really need DNS caching, check out unbound.  It's super 
> fast/lightweight (compared to BIND), if you're just doing caching..  
> For all my internal stuff, I disable systemd's resolver, and use unbound.
>
> On Mon, Sep 21, 2020 at 1:19 PM Grand Rapids Linux Users Group 
> <grlug at grlug.org <mailto:grlug at grlug.org>> wrote:
>
>     I'm more used to using BIND DNS as a recursive resolver and/or
>     machine-local caching resolver.  It may be older, but if it ain't
>     broke, don't fix it.  So, if it's available to you (depending on
>     how much control you have of the environment you run in), you
>     might want to give it a try.  It's easy to set up and boringly
>     reliable.
>
>     Warm Regards,
>     Kyle Maas
>
>
>
>     On 9/20/20 7:18 PM, Grand Rapids Linux Users Group wrote:
>>     I’ve been underwhelmed by systemd DNS for a few months, and am
>>     working through it’s implementation on both ubuntu and centos to
>>     determine why / where it gets its hooks, but haven’t found a real
>>     fix for it, yet.  There are ways to inject nameservers / search
>>     domain.tld / etc. using NetworkManager, network/ing.service,
>>     internal dhcp or dhclient, but none are consistently implemented
>>     and you end up with hosts that fail to resolve internal and
>>     external fqdns until you trounce /etc/resolv.conf with a sane
>>     version of nameservers for your network.
>>
>>     Currently netplan appears to be the most reasonable management
>>     option, but I’m still working through it’s implementation and
>>     deployment.  One of the challenges, I’m running into is that I’m
>>     migrating my VirtualBox VMs to libvirt / KVM, which adds the
>>     additional complication of configuring bonding, but have mostly
>>     worked through those details and have a good netplan
>>     configuration for the kvm nodes, just need to finalize how to
>>     reapply the netplan on running hosts without disrupting
>>     networking on the various guests when network changes happen.
>>
>>     If anyone else is also working on ways to replace systemd’s
>>     brain-dead DNS implementation, I’d be interested in seeing what
>>     you’re experiencing.  Seems a good problem to gather
>>     collaborators for, especially those using different distros, such
>>     as centos, ubuntu, suse, etc.
>>
>>     -Van
>>
>>>     On Sep 18, 2020, at 18:59, Grand Rapids Linux Users Group
>>>     <grlug at grlug.org <mailto:grlug at grlug.org>> wrote:
>>>
>>>     Have a VPS that came configured to use systemd DNS, .. and every
>>>     now and
>>>     then resolution fails (there are Nagios checks checking for the
>>>     various
>>>     websites on that server).
>>>
>>>     Anyone ever seen such a transient failures?
>>>
>>>            Thanks!
>>>     -- 
>>>     grlug mailing list
>>>     grlug at grlug.org <mailto:grlug at grlug.org>
>>>     https://shinobu.grlug.org/mailman/listinfo/grlug
>>
>>
>
>     -- 
>     grlug mailing list
>     grlug at grlug.org <mailto:grlug at grlug.org>
>     https://shinobu.grlug.org/mailman/listinfo/grlug
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://shinobu.grlug.org/pipermail/grlug/attachments/20200921/56a4fe9c/attachment.html>