CentOS 9 Stream DNS Failures from systemd-resolved Misconfiguration
Name resolution fails while IP connectivity works on CentOS Stream 9. This diagnostic guide maps systemd-resolved symptoms to causes and provides ordered checks and safe fixes.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Name resolution fails while IP connectivity works on CentOS Stream 9. This diagnostic guide maps systemd-resolved symptoms to causes and provides ordered checks and safe fixes.
Whilst investigating some TCP network issues in containers I tried to use ss to peek into container network TCP stack. We are running Amazon Linux in AWS: # uname -a Linux 4.14.173-137.229.amzn2.x86_64 #1 SMP Wed Apr 1 18:06:08 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ss has the following cli switch for that: -N NSNAME, --net=NSNAME Switch to the specified ne
On my Linux (actually OpenWrt) device, I have two default routes: root@<>:~# ip route default via 10.111.7.76 dev eth1 proto static metric 10 linkdown default via <redacted> dev wwan0 proto static src <redacted> metric 40 eth1 has an MTU of 1500 and wwan0 has an MTU of 1300. eth1 is currently down and hence the linkdown in the output above.
I'm currently developping a network configuration role used by Ansible to customize our fresh new virtual machine that came from our Debian 11 template. The following role changes from DHCP to static interface configuration and then restart the networking service.For testing purpose i set IP/netmask/gateway as extra vars (and it's dynamically changed depends
Enabling Privacy Extension ( net.ipv6.conf.eth0.use_tempaddr=2 in /etc/sysctl.conf ) for IPv6 gives me a new IP address for a fixed period of time, is there a way to get a new IPv6 on demand? i.e. refresh a new IPv6 when needed?
I'm transferring big files (78GB) through network, with NFS, but the transfer is finally limited to 6 Gbps (on a 2x10Gb NIC). I cannot find the bottleneck for now. Here my setup: 1 Server MB: Supermicro X10DRH-C (pcie 3.0), only one cpu NIC: 2 x 10Gb (intel X710-T2L) 64GB of DDR4 (2400Mhz) HBA: LSI 9311-8i => 2 mini SAS hd connected to SAS 12Gb backplane
I'm running Debian Testing (kernel 5.10.0-2-amd64 / systemd 247.2-5) on a Mac Pro as a NAS / VM host. Today, I added a Thunderbolt 3 card (Gigabyte Titan Ridge) - and noticed something strange: the network identifiers of the Mac's built-in Ethernet ports (enp9s0 / enp10s0) change to enp14s0/enp15s0 depending on whether my iMac is attached and powered on via
I'm trying to run SSH on a non-standard port. But I can't even get a TCP packet through. IP routing works fine on port 22 and so does the actual connection: downstream@localhost:~$ ip route get 172.234.232.12 ipproto tcp dport 22 172.234.232.12 via 172.234.224.1 dev eth0 src 172.234.224.188 uid 1000 cache downstream@localhost:~$ nc -zvw2 172.234.232.12 22 Co
I am using hyper-v as a hypervisor and installed ubuntu 21 on it. There, whenever I start the VM, the eth0 (only one network interface connected,Default Switch of Hyper-v) is not getting IP and showing as down. Please bare with my snaps, as I can't ssh to the machine to copy the output and paste here as text. There is no /etc/network/interfaces file on my ma
answered · 06 Apr 2026, 14:23 UTC