On 16/06/2015 4:03 AM, Anders Ingemann
wrote:
Hi
all,
I
have instanciated the Jessie AMI (ami-e31a6594,
available in eu-west-1).
Once
logged in, I noticed there was no resolv.conf file,
which explained why my cloudinit script failed.
Is
there any rational explanation ? Did I miss something ?
Thanks,
Chris
The resolv.conf is deleted when the AMI is created,
because the DNS server addresses at image creation are most
likely not the same as the ones when an instance is
launched. They *should* be fetched from the DHCP server at
boot time, have a look in /etc/dhcpc/resolv.conf (not sure
if that exists on the jessie ami though, might be wheezy
only)
Indeed; not only are the images generated in US-East-1 and then
copied to each region, when you launch them within your VPC some of
the options (such as domain name) and the DNS servers in question
would have to be scoped to your IP addressing and your VPC DHCP
Options that you select. I'm not sure why the dhcp client hasn't
populated the file right now.... will have to look on the weekend.
--
Mobile: +61 422 166 708, Email:
james_AT_rcpt.to
|