Hrmmm... it just bit me while trying to test out the checkbox charm on bare metal from my private maas server. and it's not just a matter of juju.
for example, MAAS is successfully updating the zone files: npdxh IN CNAME 10-0-0-123 and I can't ssh to my node by hostname: ubuntu@critical-maas:/etc/bind/maas$ ssh npdxh ssh: Could not resolve hostname npdxh: Name or service not known so I have to know the IP address. The NODE, does at least resolve DNS on the MAAS network properly: ubuntu@npdxh:~$ host npdxh npdxh.master is an alias for 10-0-0-123.master. 10-0-0-123.master has address 10.0.0.123 And I'm sure we all already know that much. IN any case, this is an annoyance, it's fixable, but really, the MAAS region controller (and cluster in this case since they're all one system for me) should be able to resolve its own DNS entries. >From a more important use case, for certification purposes, if I am going to get testers to use juju and the checkbox charms for testing, I can not also require them to provide separate systems to serve as region or cluster or juju systems just for DNS resolution to work. Nor does it look good to tell engineers at partner sites to manually work around this. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1274527 Title: MAAS doesn't put its DNS server in resolv.conf To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1274527/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
