Meshcentral: Bug: Devices imported via MeshCmd defaulting to IP instead of hostname

[ad-85]

Having a new issue here in our agentless environment where the device will no longer be imported using its FQDN hostname after adding it via meshcmd. This used to work fine, but about a month ago when we updated to address different issues it started falling back to IP.

We looked into it being a DNS issue but even the server seems to pick up the hostname fine during the add process - it just doesn't show up in the device info afterward. We updated again today to latest but the issue is still persistent.

Versions:

Server log excerpt during add:

Ping/NSlookup test

Sample device:

[Ylianst]

Your right. This is an important one and good timing. I am working today on improved Intel AMT ACM activation and will add that in.

[Ylianst]

Working on this one now.

[Ylianst]

Ok, this will be in MeshCentral v0.7.83 when it's next published. Let me know if that works for you.

[Ylianst]

MeshCentral v0.7.83 is out. Let me know if it works for you.

[ad-85]

It's working now! Thank you Ylian!