I agree, it is usually that simple!
(others have hard coded to Google DNS at 22.214.171.124 and 126.96.36.199, an alternative approach).
Exceptions are hidden devices, so they can't (easily) be tweaked via the GUI. What if they spring back to life when reinstalled, but the DNS IP is hard coded? Such as the Yoga 13 story I started this article with:
another nuisance is with every update rollup, which means the fixes have to be done again.
I admin about 8 systems that aren't in my house (client connector over VPN), so it's a bit of a hassle when their internet breaks. Looking forward to this longstanding issue going away for good. Just one less point of failure!
VMware ESXi 6.0U2 (soon 6.5)
Supermicro SuperServer SYS-5028D-TN4T with Xeon D-1541 8 core (soon Xeon D-1567 12 core)
128GB DDR4 2400MHz ECC RAM, 4 HDDs, 2 SSDs, & 1 Samsung 950 Pro M.2 NVMe 512GB SSD (soon Samsung 960)
Testing out VSAN clusters as well (essentially a RAID6 of 3 M.2 NVMe internal drives, connected using 10GbE)