f0

@alban the problem is the glibc resolving bahaviour. glibc uses always the first nameserver (unless you set the rotate option , but this makes the problem bigger, then you have...

@jellonek hm i do not think this is app specific... normally a app should use gethostbyname and then goes through the nss config (nssswitch.conf ) , this can end in...

@jellonek hm yes you are right, i assumed glibc and ignored the rest of the world

@alban @steveeJ @jellonek This is no longer needed , systemd v231 has a new feature, with this you can use systemd-resolved like alocal nameserver ``` systemd-resolved now listens on the...

@jonboulle yes

We found the reason (maybe?) We do not use bond0, we disable this with ``` cat /etc/modprobe.d/bonding.conf options bonding max_bonds=0 ``` and then systemd creates the netdev bonding. With this...

it turns out that max_bonds=0 is the default setting that comes with systemd and after removing up/down delay, and mii-monitor from the bonding.netdev, more systems are stable , but not...

LACPTransmitRate=fast solves this Problem for us......