OK, for reference: === gce == $ host metadata. Host metadata. not found: 3(NXDOMAIN) $ host metadata metadata.google.internal has address 169.254.169.254 Host metadata.google.internal not found: 3(NXDOMAIN) Host metadata.google.internal not found: 3(NXDOMAIN)
$ host metadata.google.internal. metadata.google.internal has address 169.254.169.254 Host metadata.google.internal not found: 3(NXDOMAIN) Host metadata.google.internal not found: 3(NXDOMAIN) $ cat /etc/resolv.conf domain c.smoser-00.internal. search c.smoser-00.internal. 410770698331.google.internal. google.internal. nameserver 169.254.169.254 === on ec2 === $ host instance-data instance-data.ec2.internal has address 169.254.169.254 $ host instance-data. Host instance-data. not found: 3(NXDOMAIN) $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 172.16.0.23 search ec2.internal So, using just 'metadata.' will actually not work. It seems like maybe the best thign to do is to use 'metadata.google.internal.' and make it configurable. -- https://code.launchpad.net/~jablonskis/cloud-init/add-gce-datasource/+merge/204464 Your team cloud init development team is requested to review the proposed merge of lp:~jablonskis/cloud-init/add-gce-datasource into lp:cloud-init. _______________________________________________ Mailing list: https://launchpad.net/~cloud-init-dev Post to : cloud-init-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~cloud-init-dev More help : https://help.launchpad.net/ListHelp