No nameserver found after kernel upgrade

[Jouk]

Hi all,

Today I upgraded my kernel form 6.0.16 to 6.0.18 on a F37 system. After rebooting no nameservers are found at the end of /run/systemd/resoilve/resolv.conf.

I found 2 ways to get the name resolve work again:
    -reboot in kernel 6.0.16
    -Change the internet adapter configuration from DHCP to Manual (and inserting the same info as before)

This looks to me to be a bug. (or am I wrong?)

regards
                 Jouk

[Barry Scott]

On 11/01/2023 12:15, Jouk via users wrote:
> Hi all,
>
> Today I upgraded my kernel form 6.0.16 to 6.0.18 on a F37 system. After rebooting no nameservers are found at the end of /run/systemd/resoilve/resolv.conf.
>
> I found 2 ways to get the name resolve work again:
>      -reboot in kernel 6.0.16
>      -Change the internet adapter configuration from DHCP to Manual (and inserting the same info as before)
>
> This looks to me to be a bug. (or am I wrong?)

I have check two systems both on 6.0.16-300.fc37.x86_64

systemd.networkd no issue. the nameserver is the one published by my 
DHCP server (also Fedora).

NetworkManager no issue. the nameserver is the one published by my DHCP 
server (also Fedora).

Both use systemd.resolved and resolvectl reports the correct settings. 
For example:

$ resolvectl
Global
        Protocols: LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=no/unsupported
resolv.conf mode: stub

Link 2 (enp2s0)
     Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
          Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS 
DNSSEC=no/unsupported
Current DNS Server: 172.16.2.254
        DNS Servers: 172.16.2.254
         DNS Domain: chelsea.private

Link 3 (wlp3s0)
Current Scopes: none
      Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS 
DNSSEC=no/unsupported

Check the logs from network manager for clues.

My router/dns-server/dhcpd is 172.16.2.154
I have this message on my NetworkManager system:

$ journalctl -b 0 -g 172.16.2.254
2023-01-06T17:56:25+0000 systemd-resolved[815]: enp2s0: Bus client set 
DNS server list to: 172.16.2.254

Barry
>          regards
>               Jouk
>
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Jouk]

> I have check two systems both on 6.0.16-300.fc37.x86_64

Note that with kernel 6.016 I also had no problems. The problems occurred when booting into kernel 6.0.18.

[Barry]

> On 12 Jan 2023, at 07:17, Jouk via users  wrote:
>
> 
> > I have check two systems both on 6.0.16-300.fc37.x86_64
>
> Note that with kernel 6.016 I also had no problems. The problems occurred when booting into kernel 6.0.18.

I will be doing my weekly update tomorrow and will report what i find.

Barry
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[Barry Scott]

On 12/01/2023 07:17, Jouk via users wrote:
> > I have check two systems both on 6.0.16-300.fc37.x86_64
>
> Note that with kernel 6.016 I also had no problems. The problems occurred when booting into kernel 6.0.18.

Both systemd-networkd and NetworkManager machines work with 6.0.18 for me.

What services are you using for your networking?

systemd-networkd? NetworkManager? systemd-resolved?

Barry
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[lejeczek]

On 11/01/2023 13:15, Jouk via users wrote:
> Hi all,
>
> Today I upgraded my kernel form 6.0.16 to 6.0.18 on a F37 system. After rebooting no nameservers are found at the end of /run/systemd/resoilve/resolv.conf.
>
> I found 2 ways to get the name resolve work again:
>      -reboot in kernel 6.0.16
>      -Change the internet adapter configuration from DHCP to Manual (and inserting the same info as before)
>
> This looks to me to be a bug. (or am I wrong?)
>          regards
>               Jouk

I too think - something to do with recent updates, kernel or 
components/services.

-> $ host wp.pl
;; communications error to 127.0.0.53#53: connection refused
;; communications error to 127.0.0.53#53: connection refused
;; no servers could be reached

Default systemd' resolver (as service) runs in stub mode.
Suffices to:

-> $ systemctl stop systemd-resolved

and:

-> $ host wp.pl
wp.pl has address 212.77.98.9
wp.pl mail is handled by 5 mx5.wp.pl.
wp.pl mail is handled by 0 mx.wp.pl.

start it again:
-> $ systemctl start systemd-resolved
-> $ host wp.pl
;; communications error to 127.0.0.53#53: timed out
;; communications error to 127.0.0.53#53: timed out
;; no servers could be reached

I think it's candidate for Bugzilla report - if the author 
of the thread filed one then let us know so we can chip in.

thanks, L,

[Barry]

> On 14 Jan 2023, at 17:02, lejeczek via users  wrote:
>
> 
> > On 11/01/2023 13:15, Jouk via users wrote:
> > Hi all,
> >
> > Today I upgraded my kernel form 6.0.16 to 6.0.18 on a F37 system. After rebooting no nameservers are found at the end of /run/systemd/resoilve/resolv.conf.
> >
> > I found 2 ways to get the name resolve work again:
> >     -reboot in kernel 6.0.16
> >     -Change the internet adapter configuration from DHCP to Manual (and inserting the same info as before)
> >
> > This looks to me to be a bug. (or am I wrong?)
> >         regards
> >              Jouk
>
> I too think - something to do with recent updates, kernel or components/services.
>
> -> $ host wp.pl
> ;; communications error to 127.0.0.53#53: connection refused
> ;; communications error to 127.0.0.53#53: connection refused
> ;; no servers could be reached
>
> Default systemd' resolver (as service) runs in stub mode.
> Suffices to:
>
> -> $ systemctl stop systemd-resolved
>
> and:
>
> -> $ host wp.pl
> wp.pl has address 212.77.98.9
> wp.pl mail is handled by 5 mx5.wp.pl.
> wp.pl mail is handled by 0 mx.wp.pl.
>
> start it again:
> -> $ systemctl start systemd-resolved
> -> $ host wp.pl
> ;; communications error to 127.0.0.53#53: timed out
> ;; communications error to 127.0.0.53#53: timed out
> ;; no servers could be reached
>
> I think it's candidate for Bugzilla report - if the author of the thread filed one then let us know so we can chip in.

What does resolvectl report? It shows what systemd-resolved has configured.

Barry
> thanks, L,
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue

[lejeczek]

On 14/01/2023 19:43, Barry wrote:
> > On 14 Jan 2023, at 17:02, lejeczek via users  wrote:
> >
> > 
> > > On 11/01/2023 13:15, Jouk via users wrote:
> > > Hi all,
> > >
> > > Today I upgraded my kernel form 6.0.16 to 6.0.18 on a F37 system. After rebooting no nameservers are found at the end of /run/systemd/resoilve/resolv.conf.
> > >
> > > I found 2 ways to get the name resolve work again:
> > >      -reboot in kernel 6.0.16
> > >      -Change the internet adapter configuration from DHCP to Manual (and inserting the same info as before)
> > >
> > > This looks to me to be a bug. (or am I wrong?)
> > >          regards
> > >               Jouk
> >
> > I too think - something to do with recent updates, kernel or components/services.
> >
> > -> $ host wp.pl
> > ;; communications error to 127.0.0.53#53: connection refused
> > ;; communications error to 127.0.0.53#53: connection refused
> > ;; no servers could be reached
> >
> > Default systemd' resolver (as service) runs in stub mode.
> > Suffices to:
> >
> > -> $ systemctl stop systemd-resolved
> >
> > and:
> >
> > -> $ host wp.pl
> > wp.pl has address 212.77.98.9
> > wp.pl mail is handled by 5 mx5.wp.pl.
> > wp.pl mail is handled by 0 mx.wp.pl.
> >
> > start it again:
> > -> $ systemctl start systemd-resolved
> > -> $ host wp.pl
> > ;; communications error to 127.0.0.53#53: timed out
> > ;; communications error to 127.0.0.53#53: timed out
> > ;; no servers could be reached
> >
> > I think it's candidate for Bugzilla report - if the author of the thread filed one then let us know so we can chip in.
>
> What does resolvectl report? It shows what systemd-resolved has configured.
>
> Barry

reports as I expect it, okey.
I missed a few copy&paste, I rushed. (with multiple ifaces & 
dnses in my box)
I wonder now, if it is possible, nowadays, to "bypass" 
systemd's resolver - except if a separate DNS server is ran 
locally.
I think DNSes - whether it is your local one or public ones 
- might play a role here and I suggest you guys play with that.
perhaps the Internet(dns) is under attack :)

[Tom Horsley]

On Sat, 14 Jan 2023 20:39:49 +0100
lejeczek via users wrote:
> I wonder now, if it is possible, nowadays, to "bypass" 
> systemd's resolver - except if a separate DNS server is ran 
> locally.

Just disable (and mask for belt and suspenders) systemd-resolved.
Then edit /etc/NetworkManager/NetworkManager.conf and add
dns=none after the "[main]" section, then you can remove the
/etc/resolv.conf symlink and replace it with a real file
you can point to your real server and network manager and
systemd will leave you alone :-).

I do that, plus run dnsmasq as a local dns server for my lan
which picks up all the names from /etc/hosts so everyone
on the local network can talk (as long as my main server is up,
anyway :-). Of course, I also have to tell the DHCP on my
router to inform everyone to point to my local server for DNS.

[Jouk]

For me the problem was solved after updating to kernel 6.1.5