A minor advantage of resolvconf even for a server is that nameserver addresses are associated with the interfaces over which they are accessible, which is clearer.
The package is designed not to break name service on upgrade on machines that have static resolv.conf. I can imagine that machines whose resolv.conf is managed by custom scripts have problems on upgrade. Supporting such machines would have required enhancing glibc so that it could be configured to read another file than /etc/resolv.conf. This would have been a lot of work and would just have made other people unhappy.The text file method was working just fine for servers. The resolvconf devs should have made that tool backwards compatible
Changes like that aren't made for no good reason. Prior to resolvconf, all sorts of programs fiddled with /etc/resolv.conf, none of them preserving one another's changes. Resolvconf imposes order on all that.Change for the sake of change seems foolish. I'm just sayin'. </rant> Sorry for that. I do feel better now.
It does, on a fresh install.I'm not saying that it isn't an improvement for GUI users on DHCP. It definitely seems to be for them.
It would be extremely helpful if the default /etc/network/interfaces file actually contained an example for static IP configuration - all commented out.