I just found that one of my systems that uses systemd-networkd
did not have DNS setup.
Below is the all the commands I ran to debug this problem that
showed up
after the system was dnf updated and rebooted.
This is what I found:
$ host google.com
Host google.com not found: 2(SERVFAIL)
$ more /etc/resolv.conf
# This is /run/systemd/resolve/stub-resolv.conf managed by
man:systemd-resolved(8).
# <snip>
nameserver 127.0.0.53
options edns0 trust-ad
search .
$ resolvectl
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS
DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (internal)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS
DNSSEC=no/unsupported
DNS will not work - next to figure out why resolved is not setup.
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue
state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: internal: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
qdisc mq state UP group default qlen 1000
link/ether ac:1f:6b:f6:e0:94 brd ff:ff:ff:ff:ff:ff
inet 172.16.2.200/24 brd 172.16.2.255 scope global internal
valid_lft forever preferred_lft forever
inet6 fe80::ae1f:6bff:fef6:e094/64 scope link
valid_lft forever preferred_lft forever
$ more 10-internal.link
[Link]
Description=Set internal ethernet interface name
Name=internal
[Match]
# eno1
MACAddress=ac:1f:6b:f6:e0:94
$ more internal-if.network
[Match]
Name=internal
[Network]
Description=Internal network
Address=172.16.2.200/24
Gateway=172.16.2.254
DNS=172.16.2.254
Domains=chelsea.private
$ networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 internal ether routable configuring
Odd - configuring!
$ networkctl status
● State: routable
Online state: online
Address: 172.16.2.200 on internal
fe80::ae1f:6bff:fef6:e094 on internal
Gateway: 172.16.2.254 on internal
DNS: 172.16.2.254
Search Domains: chelsea.private
Mar 18 09:20:41 fender.chelsea.private systemd-networkd[573]:
internal: Gained IPv6LL
Mar 21 08:50:15 fender.chelsea.private systemd[1]: Starting
systemd-networkd.service - Network Configuration...
Mar 21 08:50:15 fender.chelsea.private systemd-networkd[63749]:
internal: Link UP
Mar 21 08:50:15 fender.chelsea.private systemd-networkd[63749]:
internal: Gained carrier
Mar 21 08:50:15 fender.chelsea.private systemd-networkd[63749]:
lo: Link UP
Mar 21 08:50:15 fender.chelsea.private systemd-networkd[63749]:
lo: Gained carrier
Mar 21 08:50:15 fender.chelsea.private systemd-networkd[63749]:
internal: Gained IPv6LL
Mar 21 08:50:15 fender.chelsea.private systemd-networkd[63749]:
Enumeration completed
Mar 21 08:50:15 fender.chelsea.private systemd[1]: Started
systemd-networkd.service - Network Configuration.
Mar 21 08:50:15 fender.chelsea.private systemd-networkd[63749]:
internal: Configuring with
/etc/systemd/network/internal-if.network.
$ networkctl status internal
● 2:
internal
Link File:
/etc/systemd/network/10-internal.link
Network File:
/etc/systemd/network/internal-if.network
Type: ether
Kind: n/a
State: routable (configured)
Online state:
online
Path: pci-0000:01:00.0
Driver: igb
Vendor: Intel Corporation
Model: I210 Gigabit Network Connection
Hardware Address: ac:1f:6b:f6:e0:94 (Super Micro
Computer, Inc.)
MTU: 1500 (min: 68, max: 9216)
QDisc: mq
IPv6 Address Generation Mode: eui64
Number of Queues (Tx/Rx): 8/8
Auto negotiation: yes
Speed: 1Gbps
Duplex: full
Port: tp
Address: 172.16.2.200
fe80::ae1f:6bff:fef6:e094
Gateway: 172.16.2.254
DNS: 172.16.2.254
Search Domains: chelsea.private
Activation Policy: up
$ resolvectl
Global
Protocols: LLMNR=resolve -mDNS -DNSOverTLS
DNSSEC=no/unsupported
resolv.conf mode: stub
Link 2 (internal)
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
What?!?!? Configured!
$ networkctl
IDX LINK TYPE OPERATIONAL SETUP
1 lo loopback carrier unmanaged
2 internal ether routable configured
Now configured!
So after 3 days of being
stuck in configured it working now
that I run only the above commands. One of the status commands
unstuck networkd?
The last event on the system
was a dns update 2023-03-18 that includes these packages:
---> Package
systemd.x86_64 251.13-5.fc37 will be upgraded
---> Package systemd.x86_64 251.13-6.fc37 will be an upgrade
---> Package systemd-boot-unsigned.x86_64 251.13-5.fc37 will
be upgraded
---> Package systemd-boot-unsigned.x86_64 251.13-6.fc37 will
be an upgrade
---> Package systemd-libs.x86_64 251.13-5.fc37 will be
upgraded
---> Package systemd-libs.x86_64 251.13-6.fc37 will be an
upgrade
---> Package systemd-networkd.x86_64 251.13-5.fc37 will be
upgraded
---> Package systemd-networkd.x86_64 251.13-6.fc37 will be an
upgrade
---> Package systemd-oomd-defaults.noarch 251.13-5.fc37 will
be upgraded
---> Package systemd-oomd-defaults.noarch 251.13-6.fc37 will
be an upgrade
---> Package systemd-pam.x86_64 251.13-5.fc37 will be
upgraded
---> Package systemd-pam.x86_64 251.13-6.fc37 will be an
upgrade
---> Package systemd-resolved.x86_64 251.13-5.fc37 will be
upgraded
---> Package systemd-resolved.x86_64 251.13-6.fc37 will be an
upgrade
---> Package systemd-rpm-macros.noarch 251.13-5.fc37 will be
upgraded
---> Package systemd-rpm-macros.noarch 251.13-6.fc37 will be
an upgrade
---> Package systemd-udev.x86_64 251.13-5.fc37 will be
upgraded
---> Package systemd-udev.x86_64 251.13-6.fc37 will be an
upgrade
Why was the interface stuck in configuring?
Barry
