maas-devel team mailing list archive

[Julian Edwards <julian.edwards@xxxxxxxxxxxxx>]

https://bugs.launchpad.net/maas/+bug/1250435

One solution for this is to simply ditch the CNAMEs and use the actual chosen 
host name in the A records.  This would mean a slightly intrusive change so 
that we don't fill the zone with the old N-N-N-N style first.

Can you guys remember why we did this in the first place, and the 
ramifications of not doing it?

Alternatively, the reason this bug crops up is because the node's hostname is 
set to the CNAME rather than the A record.  We could do a quicker fix if we 
use the A record as its hostname.  The CNAME would still exist for humans, but 
this should fix picky apps like Postgres and SSH.

Thoughts?