Re: Don't update to the latest f33!

: Mon, 22 Feb 2021 18:02:08 From: Michael Catanzaro Reply-To: Development discussions related to Fedora To: David Both Cc: Development discussions related to Fedora , Steve Dickson Subject: Re: Don't update to the latest f33! On Mon, Feb 22, 2021 at 5:43 pm, David Both wrote: I

Re: Don't update to the latest f33!

On Mon, Feb 22, 2021 at 5:43 pm, David Both wrote: I will check because I thought I had TLS up and working. Apparently not. How did you discover this? I will fix it as soon as possible. All of my mails to you are bouncing. Notice you don't have any direct mails from me in your inbox.

Re: Don't update to the latest f33!

m: Michael Catanzaro Reply-To: Development discussions related to Fedora To: David Both Cc: Development discussions related to Fedora , Steve Dickson Subject: Re: Don't update to the latest f33! On Mon, Feb 22, 2021 at 1:45 pm, David Both wrote: Do you have any suggestions? Run '

Re: Don't update to the latest f33!

On Mon, Feb 22, 2021 at 1:45 pm, David Both wrote: Do you have any suggestions? Run 'resolvectl' and post the output so we can see what your configuration is. I hinted at this in my previous mail but it seems I didn't explicitly ask you to post what it outputs. Please post it so we can see

Re: Don't update to the latest f33!

related to Fedora To: David Both Cc: Development discussions related to Fedora , Steve Dickson Subject: Re: Don't update to the latest f33! On Thu, Feb 18, 2021 at 10:39 am, David Both wrote: Ok, so I manage my network using DHCP on an internal server for all except that server and my

Re: Don't update to the latest f33! (fwd)

: Thu, 18 Feb 2021 10:46:53 From: Michael Catanzaro Reply-To: Development discussions related to Fedora To: David Both Cc: Development discussions related to Fedora , Steve Dickson Subject: Re: Don't update to the latest f33! On Thu, Feb 18, 2021 at 10:39 am, David Both wrote

Re: Don't update to the latest f33!

On Thu, Feb 18, 2021 at 10:39 am, David Both wrote: Ok, so I manage my network using DHCP on an internal server for all except that server and my Linux firewall/router which both use a complete static configuration for networking. My DHCP server does provide DNS resolver information which,

Re: Don't update to the latest f33!

eply-To: Development discussions related to Fedora To: David Both , Development discussions related to Fedora Cc: Steve Dickson Subject: Re: Don't update to the latest f33! On Thu, Feb 18, 2021 at 8:30 am, Michael Catanzaro wrote: We don't set DNS there intentionally because it eliminates a

Re: Don't update to the latest f33!

Dnia Thu, Feb 18, 2021 at 02:37:54PM +, Sven Kieske napisał(a): > On Do, 2021-02-18 at 08:30 -0600, Michael Catanzaro wrote: > > Fedora will never configure static DNS servers for you in > > > > resolved.conf. That config file was manually edited with improper > > > > syntax to wind up in

Re: Don't update to the latest f33!

On Do, 2021-02-18 at 08:30 -0600, Michael Catanzaro wrote: > Fedora will never configure static DNS servers for you in > > resolved.conf. That config file was manually edited with improper > > syntax to wind up in this broken state. My guess is that it was edited > > by the VPS provider, but

Re: Don't update to the latest f33!

On Thu, Feb 18, 2021 at 8:30 am, Michael Catanzaro wrote: We don't set DNS there intentionally because it eliminates any benefit of using split DNS. Your static global DNS= configuration in resolved.conf is used for *every* request, *in addition* to per-link DNS configuration. So if you have

Re: Don't update to the latest f33!

Fedora will never configure static DNS servers for you in resolved.conf. That config file was manually edited with improper syntax to wind up in this broken state. My guess is that it was edited by the VPS provider, but who knows. We don't set DNS there intentionally because it eliminates any

Re: Don't update to the latest f33!

To: Steve Dickson , Development discussions related to Fedora Subject: Re: Don't update to the latest f33! On 18/02/2021 09:18, Steve Dickson wrote: On 2/17/21 6:55 PM, Ed Greshko wrote: On 18/02/2021 05:11, Steve Dickson wrote: I agree... ignoring syntax error or parsing error just

Re: Don't update to the latest f33!

On 18/02/2021 09:18, Steve Dickson wrote: On 2/17/21 6:55 PM, Ed Greshko wrote: On 18/02/2021 05:11, Steve Dickson wrote: I agree... ignoring syntax error or parsing error just does not seem like the appropriate thing to do... Error out! Tell me what is broken so I can fix it!! Replace the

Re: Don't update to the latest f33!

On 2/17/21 6:55 PM, Ed Greshko wrote: > On 18/02/2021 05:11, Steve Dickson wrote: >> I agree... ignoring syntax error or parsing error just does not seem >> like the appropriate thing to do... Error out! Tell me what is broken >> so I can fix it!! > > Replace the "," with a " " in the DNS=

Re: Don't update to the latest f33!

On 18/02/2021 05:11, Steve Dickson wrote: I agree... ignoring syntax error or parsing error just does not seem like the appropriate thing to do... Error out! Tell me what is broken so I can fix it!! Replace the "," with a " " in the DNS= entry of /etc/systemd/resolved.conf file. And if you

Re: Don't update to the latest f33!

On 2/16/21 9:03 AM, Ed Greshko wrote: > On 16/02/2021 21:37, Steve Dickson wrote: >> >> On 2/15/21 9:16 PM, Dominique Martinet wrote: >>> Steve Dickson wrote on Mon, Feb 15, 2021 at 09:04:52PM -0500: > I think if no IP was successfully parsed the fallback ought to kick in, > so it's a

Re: Don't update to the latest f33!

On 2/16/21 9:02 AM, Troy Curtis Jr wrote: > > > On Mon, Feb 15, 2021 at 10:02 PM Dominique Martinet > wrote: > > Michael Catanzaro wrote on Mon, Feb 15, 2021 at 08:46:57PM -0600: > > We removed the fallbacks due to complaints from users who didn't want

Re: Don't update to the latest f33!

On 17/02/2021 04:24, Marius Schwarz wrote: Am 16.02.21 um 15:03 schrieb Ed Greshko: Thanks for the help! FWIW, I suppose I don't know why a BZ is needed since the /etc/systemd/resolved.conf has a sample for the DNS= parameter showing: I think that "," is received by a dhcp answere from

Re: Don't update to the latest f33!

Am 16.02.21 um 15:03 schrieb Ed Greshko: Thanks for the help! FWIW, I suppose I don't know why a BZ is needed since the /etc/systemd/resolved.conf has a sample for the DNS= parameter showing: I think that "," is received by a dhcp answere from the dhcpd, which knows two dns and sets

Re: Don't update to the latest f33!

W dniu pon, 15.02.2021 o godzinie 17∶40 -0500, użytkownik Steve Dickson napisał: > Hello, > > I just updated to latest Fedora 33 and > I no longer have any DNS name solution. > The network is up... but... > > $ ping www.yahoo.com > ping: www.yahoo.com: Name or service not known > > I changed

Re: Don't update to the latest f33!

On 16/02/2021 21:37, Steve Dickson wrote: On 2/15/21 9:16 PM, Dominique Martinet wrote: Steve Dickson wrote on Mon, Feb 15, 2021 at 09:04:52PM -0500: I think if no IP was successfully parsed the fallback ought to kick in, so it's a systemd-resolved bug -- do you want to report this upstream

Re: Don't update to the latest f33!

On Mon, Feb 15, 2021 at 10:02 PM Dominique Martinet wrote: > Michael Catanzaro wrote on Mon, Feb 15, 2021 at 08:46:57PM -0600: > > We removed the fallbacks due to complaints from users who didn't want DNS > > ever going to Cloudflare or Google. So the lack of fallback is expected > and > >

Re: Don't update to the latest f33!

On 2/16/21 6:05 AM, David Both wrote: > This situation is due to the change from the old resolver to the new > systemd-resolved. > > I have a page on my technical web site that describes the problem and the > circumvention. > > http://www.linux-databook.info/?page_id=5951 > > This does not,

Re: Don't update to the latest f33!

On 2/15/21 9:16 PM, Dominique Martinet wrote: > Steve Dickson wrote on Mon, Feb 15, 2021 at 09:04:52PM -0500: >>> I think if no IP was successfully parsed the fallback ought to kick in, >>> so it's a systemd-resolved bug -- do you want to report this upstream or >>> shall I now I've had a look?

Re: Don't update to the latest f33!

This situation is due to the change from the old resolver to the new systemd-resolved. I have a page on my technical web site that describes the problem and the circumvention. http://www.linux-databook.info/?page_id=5951 This does not, erm, resolve the problem but it does get you back to a

Re: Don't update to the latest f33!

Michael Catanzaro wrote on Mon, Feb 15, 2021 at 08:46:57PM -0600: > We removed the fallbacks due to complaints from users who didn't want DNS > ever going to Cloudflare or Google. So the lack of fallback is expected and > should not be reported as a bug. setting DNS= (or DNS="") explicitely

Re: Don't update to the latest f33!

On Tue, Feb 16, 2021 at 10:53 am, Dominique Martinet wrote: I think if no IP was successfully parsed the fallback ought to kick in, so it's a systemd-resolved bug -- do you want to report this upstream or shall I now I've had a look? Hi Dominique, We removed the fallbacks due to

Re: Don't update to the latest f33!

Steve Dickson wrote on Mon, Feb 15, 2021 at 09:04:52PM -0500: > > I think if no IP was successfully parsed the fallback ought to kick in, > > so it's a systemd-resolved bug -- do you want to report this upstream or > > shall I now I've had a look? > > Fedora bz or an upstream bz? If is the latter

Re: Don't update to the latest f33!

On 2/15/21 8:53 PM, Dominique Martinet wrote: > Hi Steve, > > Steve Dickson wrote on Mon, Feb 15, 2021 at 08:40:17PM -0500: >> When I have DNS=67.207.67.3,67.207.67.2 I get > > FWIW the man page states it is a space-separated list of IPs, you might > want to try DNS="67.207.67.3 67.207.67.2" >

Re: Don't update to the latest f33!

Hi Steve, Steve Dickson wrote on Mon, Feb 15, 2021 at 08:40:17PM -0500: > When I have DNS=67.207.67.3,67.207.67.2 I get FWIW the man page states it is a space-separated list of IPs, you might want to try DNS="67.207.67.3 67.207.67.2" I quickly had a look at the code and I don't think anything

Re: Don't update to the latest f33!

On 2/15/21 8:16 PM, Ed Greshko wrote: > On 16/02/2021 09:10, Steve Dickson wrote: >> On 2/15/21 7:55 PM, Ed Greshko wrote: >>> On 16/02/2021 08:50, Steve Dickson wrote: But I think this is the problem... systemctl start systemd-resolved systemctl -o cat status

Re: Don't update to the latest f33!

On 16/02/2021 09:10, Steve Dickson wrote: On 2/15/21 7:55 PM, Ed Greshko wrote: On 16/02/2021 08:50, Steve Dickson wrote: But I think this is the problem... systemctl start systemd-resolved systemctl -o cat status systemd-resolved Starting Network Name Resolution... Positive Trust Anchors: .

Re: Don't update to the latest f33!

On 2/15/21 7:55 PM, Ed Greshko wrote: > On 16/02/2021 08:50, Steve Dickson wrote: >> But I think this is the problem... >> >> systemctl start systemd-resolved >> systemctl -o cat status systemd-resolved >> Starting Network Name Resolution... >> Positive Trust Anchors: >> . IN DS 20326 8 2 >>

Re: Don't update to the latest f33!

On 16/02/2021 08:50, Steve Dickson wrote: But I think this is the problem... systemctl start systemd-resolved systemctl -o cat status systemd-resolved Starting Network Name Resolution... Positive Trust Anchors: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d

Re: Don't update to the latest f33!

On 2/15/21 7:31 PM, Ed Greshko wrote: > I think I may have sent this off-list > > On 16/02/2021 08:17, Steve Dickson wrote: >> On 2/15/21 7:12 PM, Ed Greshko wrote: >>> On 16/02/2021 06:40, Steve Dickson wrote: I just updated to latest Fedora 33 and I no longer have any DNS name

Re: Don't update to the latest f33!

On 16/02/2021 08:35, Steve Dickson wrote: On 2/15/21 7:24 PM, Ed Greshko wrote: On 16/02/2021 08:17, Steve Dickson wrote: On 2/15/21 7:12 PM, Ed Greshko wrote: On 16/02/2021 06:40, Steve Dickson wrote: I just updated to latest Fedora 33 and I no longer have any DNS name solution. The

Re: Don't update to the latest f33!

On 2/15/21 7:25 PM, Sam Varshavchik wrote: >> # cat /run/NetworkManager/no-stub-resolv.conf >> cat: /run/NetworkManager/no-stub-resolv.conf: No such file or directory >> >> Who is suppose to create that? It is on /run so it be created on every >> reboot... > > NetworkManager. Maybe you have

Re: Don't update to the latest f33!

On 2/15/21 7:24 PM, Ed Greshko wrote: > On 16/02/2021 08:17, Steve Dickson wrote: >> On 2/15/21 7:12 PM, Ed Greshko wrote: >>> On 16/02/2021 06:40, Steve Dickson wrote: I just updated to latest Fedora 33 and I no longer have any DNS name solution. The network is up... but...

Re: Don't update to the latest f33!

I think I may have sent this off-list On 16/02/2021 08:17, Steve Dickson wrote: On 2/15/21 7:12 PM, Ed Greshko wrote: On 16/02/2021 06:40, Steve Dickson wrote: I just updated to latest Fedora 33 and I no longer have any DNS name solution. The network is up... but... $ pingwww.yahoo.com

Re: Don't update to the latest f33!

Steve Dickson writes: On 2/15/21 6:19 PM, Sam Varshavchik wrote: > Steve Dickson writes: > >> Hello, >> >> I just updated to latest Fedora 33 and >> I no longer have any DNS name solution. >> The network is up... but... >> >> $ ping www.yahoo.com >> ping: www.yahoo.com: Name or service not

Re: Don't update to the latest f33!

On 16/02/2021 08:17, Steve Dickson wrote: On 2/15/21 7:12 PM, Ed Greshko wrote: On 16/02/2021 06:40, Steve Dickson wrote: I just updated to latest Fedora 33 and I no longer have any DNS name solution. The network is up... but... $ pingwww.yahoo.com ping:www.yahoo.com: Name or service not

Re: Don't update to the latest f33!

On 2/15/21 7:12 PM, Ed Greshko wrote: > On 16/02/2021 06:40, Steve Dickson wrote: >> I just updated to latest Fedora 33 and >> I no longer have any DNS name solution. >> The network is up... but... >> >> $ pingwww.yahoo.com >> ping:www.yahoo.com: Name or service not known >> >> I changed

Re: Don't update to the latest f33!

On 16/02/2021 06:40, Steve Dickson wrote: I just updated to latest Fedora 33 and I no longer have any DNS name solution. The network is up... but... $ pingwww.yahoo.com ping:www.yahoo.com: Name or service not known I changed nothing! How would be the bet way to debug this??? What is the

Re: Don't update to the latest f33!

On 2/15/21 6:19 PM, Sam Varshavchik wrote: > Steve Dickson writes: > >> Hello, >> >> I just updated to latest Fedora 33 and >> I no longer have any DNS name solution. >> The network is up... but... >> >> $ ping www.yahoo.com >> ping: www.yahoo.com: Name or service not known >> >> I changed

Re: Don't update to the latest f33!

On 2/15/21 6:00 PM, Stephen John Smoogen wrote: > > > On Mon, 15 Feb 2021 at 17:39, Steve Dickson > wrote: > > Hello, > > I just updated to latest Fedora 33 and > I no longer have any DNS name solution. > The network is up... but... > > $ ping

Re: Don't update to the latest f33!

Steve Dickson writes: Hello, I just updated to latest Fedora 33 and I no longer have any DNS name solution. The network is up... but... $ ping www.yahoo.com ping: www.yahoo.com: Name or service not known I changed nothing! How would be the bet way to debug this??? Inspect what it's your

Re: Don't update to the latest f33!

On Mon, 15 Feb 2021 at 17:39, Steve Dickson wrote: > Hello, > > I just updated to latest Fedora 33 and > I no longer have any DNS name solution. > The network is up... but... > > $ ping www.yahoo.com > ping: www.yahoo.com: Name or service not known > > I changed nothing! > > How would be the bet