Almalinux 10 ct DNS not functioning

A

alexandere

Member
Jul 20, 2021
10
0
21
41
I've installed a Almalinux 10 container with the standard provided template, but DNS doesn't seem to be functioning. A different OS with the same config works without issue.

proxmox-ve: 9.0.0 (running kernel: 6.14.11-3-pve)
pve-manager: 9.0.10 (running version: 9.0.10/deb1ca707ec72a89)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.14.11-3-pve-signed: 6.14.11-3
proxmox-kernel-6.14: 6.14.11-3
proxmox-kernel-6.14.11-2-pve-signed: 6.14.11-2
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8: 6.8.12-13
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx10
intel-microcode: 3.20250512.1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.11
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.4
libpve-network-perl: 1.1.8
libpve-rs-perl: 0.10.10
libpve-storage-perl: 9.0.13
libqb0: 1.0.5-1
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.5-1
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.15-1
proxmox-backup-file-restore: 4.0.15-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.2
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.2
proxmox-widget-toolkit: 5.0.6
pve-cluster: 9.0.6
pve-container: 6.0.13
pve-docs: 9.0.8
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.17-1
pve-ha-manager: 5.0.4
pve-i18n: 3.6.0
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
pve-zsync: 2.4.0
qemu-server: 9.0.22
smartmontools: 7.4-pve1
spiceterm: 3.4.1
swtpm: 0.8.0+pve2
vncterm: 1.9.1
zfsutils-linux: 2.3.4-pve1
 
Hi,

I would compare the following, if the AlmaLinux 10 CT have the same config where the other CT works:
Code: 
cat /etc/resolv.conf
ping -c3 google.com
ping -c3 8.8.8.8
As well as the CT config `pct config <CTID>` this will help if the issue is realted to the AlmaLinux Image or to DNS configuration inside the CT.
 
Thank you for your quick reply, resolv.conf had no nameservers configured for Alma10 while there are nameservers configured for Alma9. Both were setup with default values in create container web interface using a internal ip adress and the host dns config. (i'll post configuration below). There seems to be a bug in the Almalinux setup/template?

For others with the same issue, i could fix by manualy configuring the DNS (this is reverted on a reboot of the container):

sudo nmcli connection modify <connection_name> ipv4.dns "<DNS IP>"
sudo nmcli connection down <connection_name>
sudo nmcli connection up <connection_name>


arch: amd64
cores: 1
features: nesting=1
hostname: alma10test
memory: 512
net0: name=eth0,bridge=vmbr0,gw=192.168.xxx.xxx,hwaddr=BC:24:11:71:D8:B0,ip=192.168.xxx.xxx/24,type=veth
ostype: centos
rootfs: local-zfs:subvol-100-disk-0,size=8G
swap: 512
unprivileged: 1
arch: amd64
cores: 1
features: nesting=1
hostname: alma9test
memory: 512
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.xxx.xxx,hwaddr=BC:24:11:63:B9:CF,ip=192.168.xxx.xxx/24,type=veth
ostype: centos
rootfs: local-zfs:subvol-101-disk-0,size=8G
swap: 512
unprivileged: 1
 
Last edited:
Thank you for the output!

Just to confirm what exactly template version you used for Alma10?

Could you please set nameserver using `--nameserver` flag using `pct set --nameserver 8.8.8.8 100` (change the nameserver to your nameserver IP) or add that in the CT config?
 
with the instruction you gave DNS is functioning, and present /etc/resolv.conf

the version of Almalinux is: LXC default image for almalinux 10 (20250930)
 
You must log in or register to reply here.
Top Bottom