Comment 5 for bug 1756745

The team has always agreed that the default domain should be able to be changed; it's just a matter of priority and scope.

For MAAS 2.4, we have a partial fix for this: the model has been updated, and the API now allows the default domain to be selected.

As always, the devil is in the details: we don't have a way for a node's domain to be "unset" (which is how we would have liked to represent the concept of "default domain"). So if you change the default domain, all unallocated nodes whose domain was set to the previous default domain will be set to the new default domain.

This bug won't be considered "Fix Committed" until the UI lands (as there are more critical issues to investigate at right now), but I wanted to update this bug for your information.