- Solved
- Minor
As of unRAID 7.1 it seems we can modify the network's DNS settings while containers and VMs are running. Doing this however seems to break network connectivity.
I just very quickly dug into the logs and config, and it seems after applying, unRAID wipes /boot/config/network.cfg clean. The only entries in it after are the following:
# Generated settings:
IFNAME[0]="eth0"
SYSNICS="1"
If I remove the network config, and reboot the system, unRAID automatically repopulates the network.cfg file, and connectivity works again. These are the default values for me:
# Generated settings:
IFNAME[0]="br0"
DHCP_KEEPRESOLV="no"
DHCP6_KEEPRESOLV="yes"
BONDNAME[0]="bond0"
BONDNICS[0]="eth0 eth1 eth2 eth3"
BONDING_MODE[0]="1"
BONDING_MIIMON[0]="100"
BRNAME[0]="br0"
BRNICS[0]="bond0"
BRSTP[0]="no"
BRFD[0]="0"
PROTOCOL[0]="ipv4"
USE_DHCP[0]="yes"
USE_DHCP6[0]=""
SYSNICS="1"
I will attach a syslog file from a session where the DNS is changed with active containers/vms, and where network connectivity breaks. I think me applying the DNS change starts at line 2015, though otherwise doesn't seem to helpful (at least to me).
I'm happy to provide more info if necessary.
E: Sorry for it not being proper diagnostics. I didn't know or find the command at the time, but I did just find it after 