Based on #13 and related comments, I noticed that on my AWS account I wasn't getting a Public DNS assigned each time I launched ami-08490c68.
Found this link to resolve that by adding a Virtual Private Cloud (VPC) per this link: http://stackoverflow.com/questions/20941704/ec2-instance-has-no-public- dns Adding the VPC seemed to have fixed the Public DNS issue and the "unable to resolve host" issue on my running instance and a new one as the Public DNS is showing up now. Not a fix, but seems like it is a work around for my AWS based stuff and clarified a bit some of the other comments on this thread above for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561250 Title: Xenial vagrant image is missing its hostname in /etc/hosts To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1561250/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
