Why Cloudbreak creates sometimes hosts with wrong FQDN

[#1]

When creating cluster with custom blueprint, host FQDN domain names isn't created always *.ax.internal.cloudapp.net in azure

Why?

[#2 · Accepted solution]

Hi,

Unfortunately there were some changes on Azure regarding how the domain names are set through dhcp packets and sometimes the instances do not get the right domain in time then CB falls back a creates the example.com domain. If you are using our standard Azure images, then you'll get an update early next week which addresses this issue. If you have a custom image then I'm afraid you have to recreate it with the latest changes. Also the image update itself wont' fix the problem so you'll have to update to a newer version of CB (2.4.2 is not released yet, but will be soon).