FIX: Sudo Fails After Start Up of Ubuntu VMs

This is more like a hacky quick fix. For some reason `sudo` tries to resolve the host name of the VM. Though this might fail directly after startup. I guess DNS is not updated yet. However we have a chicken-egg problem here, since with `sudo` failing I cannot change anything of the configuration.

This just uses `sudo`, checks the output and gives it half an hour time (which should be well enough for the DNS to update).