Thanks for your report. I can't reproduce this on a newly launched
Bionic EC2 instance (ami-07d0cf3af28718ef8):
ubuntu@ip-172-31-94-19:~$ host ip-172-31-94-19.ec2.internal
ip-172-31-94-19.ec2.internal has address 172.31.94.19
ubuntu@ip-172-31-94-19:~$ nslookup ip-172-31-94-19.ec2.internal
Server: 127.0.0.53
Address: 127.0.0.53#53
Non-authoritative answer:
Name: ip-172-31-94-19.ec2.internal
Address: 172.31.94.19
Could you please include the full steps to reproduce the problem, and
let us know the exact AMI you are launching? I'm marking this report as
Incomplete for the moment, please change the report status back to New
once you provided the additional details. Thanks!
** Changed in: ec2-ami-tools (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840155
Title:
new EC2 is unable to resolve local Amazon DNS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ec2-ami-tools/+bug/1840155/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
