@2-xtian - if you're testing on MAAS 2.0 then I suspect you're seeing perfectly working DNS for hosts and their containers. Bootstrap across AWS, GCE, and in particular Azure to see the issues on the public clouds.
Note: we are also proposing to land the following as an additional solution for the public clouds _and_ charms: https://github.com/frobware/nss-juju It won't fix the general case of: $ lxc exec juju-68160d-0 -- sh -c 'ping `hostname`' though see my comment about container hostname resolution in comment #6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1475260 Title: instances cannot resolve their own hostname To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1475260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
