Per support: This seems to be a known issue related to the Customer Environments feature. The solution is to set your domain to “No environment.” As soon as I did the interface picked up the custom domain. After redeploying the domain was correctly assigned and resolves as expected.