maas-devel team mailing list archive

[Andreas Hasenack <andreas@xxxxxxxxxxxxx>]

On Mon, Nov 11, 2013 at 12:00 AM, Julian Edwards <
julian.edwards@xxxxxxxxxxxxx> wrote:

> On 09/11/13 03:56, Gavin Panella wrote:
> >> What about the /etc/hosts entry pointing the machine name to 127.0.1.1,
> do
> >> you know what adds that? Is it juju? Without that entry, it also works.
> >
> > I think this is just the usual setting-the-hostname stuff: MAAS will
> > pass in the configured hostname (instead of the generated one) to the OS
> > installer, which sets the hostname accordingly, and adds an /etc/hosts
> > line so that traffic destined for itself (by name) gets routed via the
> > lo interface. Someone else - roaksoax or smoser most likely - will have
> > to confirm or correct that explanation.
>
>
> http://www.debian.org/doc/manuals/debian-reference/ch05.en.html#_the_hostname_resolution
>
> It's correct policy to have that entry, it seems.
>
>
Yeah, maybe. There is also this remark:
"For a system with a permanent IP address and a fully qualified domain name
(FQDN) <http://en.wikipedia.org/wiki/FQDN> provided by the Domain Name
System (DNS) <http://en.wikipedia.org/wiki/Domain_Name_System>, that
canonical <host_name>.<domain_name> should be used instead of just
<host_name>."


The *feels* like a bug in PG or its charm, to me.  Having said that I
> did suggest once that we return IPs from MAAS's API instead of hostnames
> but that was shot down.  I can't remember why, though.  Gavin?
>
>
I think it's incorrect to return the CNAME, and have it be the hostname of
the machine. It would be like having the www.company.com host have an
actual "www.company.com" hostname.

I'll search around what other systems to when hostnames are used for access
control, if they do the sort of lookup that postgresql does or not.



>
>
> --
> Mailing list: https://launchpad.net/~maas-devel
> Post to     : maas-devel@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maas-devel
> More help   : https://help.launchpad.net/ListHelp
>