Users can now use FQDN names for their hosts

[nastasha-solomon]

Description

Currently, the host.name for endpoints takes the computer value. After users enable the FQDN feature, they can set endpoints' host.name to use the computer.company.network value.

To enable FQDN users would need to enable the FQDN flag in the Feature Flags section of the elastic-agent.yml config file. After that, they can set a host’s name in FQDN format through the Agent Binary Download Fleet settings.

Related:

• 8.8 Endpoint release notes  #3143

Doc udpates

Add the following summary to the new features section of the 8.8 Security release notes:

Users can now use fully qualified domain name (FQDN) names for their hosts. Refer to to learn more.

[nicpenning]

FYI - There is some confusion on what FQDN on hosts actually means.

elastic/kibana#150239 (comment)

Elastic Agents using Windows Integrations were already using FQDN for host.name and then this new change in 8.8 forced them to use short name (with the .org.local).

I just wanted to loop the documentation folks in on this as it is confusing to us Elastic users on what exactly is going on here and why FQDN is not the default. This may be a lose, lose situation based on what agents did not use FQDN before and which ones did.

Just my 2 cents 😀

[nicpenning]

@nastasha-solomon - Any thoughts to my feed back above? I wanted to make sure that someone was aware of the impact this may cause if it hasn't already.