This topic has come up before peripherally but I don't see a clear and final directive on the topic. In Debian/Ubuntu, the NIC ID eth0 was replaced long ago with ens3, but ISPConfig still shows "Do not enable this option if your network interface is not eth0". That message is cryptic and perhaps misleading. Let's improve on it. In the doc we see this: Network Configuration: If you check this, ISPConfig will automatically configure your system with the network settings from the IP Address, Netmask, Gateway, Hostname, and Nameservers fields. It will also automatically configure all IP addresses that are defined under System >System > Server IP addresses. Please note that this automatic network configuration works only on Debian/Ubuntu and only if you have one network card which must be eth0. It is recommended to not check this checkbox and configure your network settings manually. I have been struggling for several days with network interfaces randomly dropping. I stumbled on this thread which describes a similar issue, as I was trying to figure out if this is caused by eth0/ens3 being hardcoded somewhere (in ISPConfig or anywhere else). I'm not going to change my NIC ID as that could cause other problems. I turned on the auto net configuration early in testing. It butchered my config files which took a long time to figure out and fix. "Ah" you say, "the doc does tell us 'It is recommended to not check this checkbox and configure your network settings manually.', so why did you enable it?" Well, since I do have Ubuntu with one NIC, and the doc is years old, I thought/hoped that the doc and UI text were simply out of date with the current functionality. So, in the productive interest of ensuring clear and accurate documentation in the future: - Is "eth0" still a requirement for Debian/Ubuntu? Or is the default "ens3" acceptable? - Is auto-configuration actively being improved? - Is auto-configuration still actively discouraged? - Why is this warning "It is recommended to not check this checkbox and configure your network settings manually" only in for-fee documentation and not on the page where someone can easily click it? Queue HHGTTG "the plans have been available in the local planning office..." If the checkbox does bad things in a new installation, why is it still there? - I'm wondering if that checkbox should simply be removed, given that as documented it only applies to a limited subset of installations, and it doesn't seem to work for that subset anyway. I mean, there have been a lot of changes related to DNS, resolv.conf, systemd-resolve, etc. Rather than being a simple checkbox, maybe it should be a link to a script where the top comments say "This is what we think should be done to auto-config your system using parameters defined in ISPConfig. Modify as required, implement at your own risk, and please MR helpful improvements." The difference between that and MR's to ISPConfig core is that such a script would not be directly integrated with the package. If the answer to these questions is "just look in the forum, it's been discussed", as I've said, I've been struggling with issues for days, setting up DNS/BIND9, dealing with resolve conflicts, checking sync between NS1/NS2, checking ufw and external firewall. I'm literally working on this stuff every minute of my day. If I've missed notes on this topic, I apologize. But in all candor, I really wish the answers were already in current ISPConfig docs so that I didn't need to read the interwebs to find hints about every detail. And yes, I understand ISPConfig is responsible for setting configuration changes, not for the effect of those changes, admin-inflicted issues, or component failures. But ISPConfig does a lot more for us under the covers - that's it's value. The problem is that there is little documentation to explain what it's doing and why. It's a black box that we need to trust, and then read the code ourselves for more details. I'm trying to get some information from outside of the code, outside of random forum posts, and into someplace accessible to users ... like a user guide. Thanks for your patience and feedback.